[petsc-users] Crash when using valgrind

Jed Brown jedbrown at mcs.anl.gov
Wed Apr 17 17:03:07 CDT 2013


Dominik Szczerba <dominik at itis.ethz.ch> writes:

> On Wed, Apr 17, 2013 at 3:43 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
>
>> Can you get a stack trace? Does this happen on a different machine?
>>
>> Stack trace of what exactly? I do not seem to be able to run gdb with
> valgrind...?
>
> gdb valgrind --tool=memcheck -q --num-callers=20 MySolver
> gdb: unrecognized option '--tool=memcheck'

Sometimes it helps to use 'valgrind --db-attach=yes'.

What happens when you pass -no_signal_handler to the PETSc program?


More information about the petsc-users mailing list