Try valgrind. Matt
On Sat, Nov 14, 2009 at 3:32 PM, Dominik Szczerba <dominik at itis.ethz.ch>wrote: > Now for something more serious: I get a crash like this one: > > Starting KSPSolve (1/2) > 0 KSP Residual norm 2.964538623545e-06 > *** glibc detected *** /home/domel/build/solve-debug/ns3t10mpi: malloc(): > memory corruption: 0x09258008 *** > ======= Backtrace: ========= > /lib/tls/i686/cmov/libc.so.6[0x5f9ff1] > /lib/tls/i686/cmov/libc.so.6[0x5fcbb3] > /lib/tls/i686/cmov/libc.so.6(__libc_calloc+0xa9)[0x5fe009] > /home/domel/build/solve-debug/ns3t10mpi(hypre_CAlloc+0x2c)[0x8b4ea28] > > /home/domel/build/solve-debug/ns3t10mpi(hypre_BoomerAMGCoarsenRuge+0xb5)[0x8af2c7b] > (and so on) > > gdb invoked as: > > mpiexec -np 2 ..... -on_error_attach_debugger -display :0.0 > > does not display any backtrace after the crash. > > Any hints how to debug are highly appreciated. > > Dominik > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20091114/e72f62c5/attachment.htm>
