[petsc-users] Crash when using valgrind
Dominik Szczerba
dominik at itis.ethz.ch
Thu Apr 18 04:12:38 CDT 2013
>
> Sometimes it helps to use 'valgrind --db-attach=yes'.
valgrind --db-attach=yes --tool=memcheck -q --num-callers=20 MySolver
bt
#0 0x0000000007cf2425 in __GI_raise (sig=<optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x0000000007cf5b8b in __GI_abort () at abort.c:91
#2 0x000000000987c98d in ?? () from /usr/lib/libcr.so.0
#3 0x000000000400f306 in call_init (l=<optimized out>, argc=2,
argv=0x7ff000138, env=0x7ff000150) at dl-init.c:85
#4 0x000000000400f3df in call_init (env=<optimized out>, argv=<optimized
out>, argc=<optimized out>, l=<optimized out>) at dl-init.c:52
#5 _dl_init (main_map=0x42242c8, argc=2, argv=0x7ff000138,
env=0x7ff000150) at dl-init.c:134
#6 0x00000000040016ea in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#7 0x0000000000000002 in ?? ()
#8 0x00000007ff0003d7 in ?? ()
#9 0x00000007ff000412 in ?? ()
#10 0x0000000000000000 in ?? ()
>
> What happens when you pass -no_signal_handler to the PETSc program?
>
valgrind --tool=memcheck -q --num-callers=20 MySolver -no_signal_handler
No change, i.e:
cr_libinit.c:183 cri_init: sigaction() failed: Invalid argument
Aborted (core dumped)
Any more ideas?
Many thanks
Dominik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20130418/b58638b4/attachment-0001.html>
More information about the petsc-users
mailing list