[petsc-users] Segmentation Violation error using SuperLU_DIST in ex 19.c

[Barry Smith]

Try option -start_in_debugger noxterm

then when the debugger starts up

c

to continue the run. Then when the program crashes you can do 

bt 

to see exactly where the crash happens in SuperLU_DIST

and 

print "some variable name in the routine"

 to check if the variables there look reasonable or if memory looks corrupted.

You can also run with valgrind to check for memory corruption. https://petsc.org/release/faq/#what-does-corrupt-argument-or-caught-signal-or-segv-or-segmentation-violation-or-bus-error-mean-can-i-use-valgrind-or-cuda-memcheck-to-debug-memory-corruption-issues



> On Nov 23, 2023, at 11:38 AM, maitri ksh <maitri.ksh at gmail.com> wrote:
> 
> Hi,
> I ran into an error while using SuperLU_DIST in ex 19.c, I am not sure how to debug this, can anyone please help. The 'configure.log' file is attached for your reference.
> Thanks,
> Maitri
> 
> <ERROR_ex19_SuperLU_DIST.txt><configure.log>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20231123/ab73ae44/attachment.html>