[petsc-users] glibc detected

[Jed Brown]

On Sat, 17 Apr 2010 11:07:55 -0400, "(Rebecca) Xuefei YUAN" <xy2102 at columbia.edu> wrote:
> Dear Jed,
> 
> What did I do wrong on this? Nothing comes out from -malloc 0:

  $ valgrind ./twgcqt2unffnictvscj.exe -options_file option_all -malloc 0

Run it this way.  The "-malloc 0" option turns off PETSc's sentinels
(that debug PetscMalloc uses to detect memory corruption) so that
valgrind can do it's job better.  Note that you can have valgrind attach
a debugger at the error points with

  $ valgrind --db-attach=yes ./twgcqt2unffnictvscj.exe -options_file option_all -malloc 0

Jed