Try valgrind.<br><br> Matt<br><br><div class="gmail_quote">On Sat, Nov 14, 2009 at 3:32 PM, Dominik Szczerba <span dir="ltr"><<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Now for something more serious: I get a crash like this one:<br>
<br>
Starting KSPSolve (1/2)<br>
0 KSP Residual norm 2.964538623545e-06<br>
*** glibc detected *** /home/domel/build/solve-debug/ns3t10mpi: malloc(): memory corruption: 0x09258008 ***<br>
======= Backtrace: =========<br>
/lib/tls/i686/cmov/libc.so.6[0x5f9ff1]<br>
/lib/tls/i686/cmov/libc.so.6[0x5fcbb3]<br>
/lib/tls/i686/cmov/libc.so.6(__libc_calloc+0xa9)[0x5fe009]<br>
/home/domel/build/solve-debug/ns3t10mpi(hypre_CAlloc+0x2c)[0x8b4ea28]<br>
/home/domel/build/solve-debug/ns3t10mpi(hypre_BoomerAMGCoarsenRuge+0xb5)[0x8af2c7b]<br>
(and so on)<br>
<br>
gdb invoked as:<br>
<br>
mpiexec -np 2 ..... -on_error_attach_debugger -display :0.0<br>
<br>
does not display any backtrace after the crash.<br>
<br>
Any hints how to debug are highly appreciated.<br><font color="#888888">
<br>
Dominik<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener<br>