Skip to content
pradeep fernando edited this page Aug 26, 2016 · 1 revision

Running with valgrind

mpiexec -n 5 valgrind -q /path/to/my_app

analyze core dump:

gdb ./gtc core

bt bt full print variable

running a program under gdb

./mpiexec -n 4 xterm -e gdb ./gtc mpiexec -n 1 xterm -e gdb ./your_app : -n 3 ./your_app : -n 1 xterm -e gdb ./your_app

http://include-test.ncsa.illinois.edu/UserInfo/Resources/Hardware/CommonDoc/mpich2_gdb.html

http://lists.mcs.anl.gov/pipermail/mpich-discuss/2010-April/006966.html

http://www.clustermonkey.net/MPI/debugging-can-you-hear-me-now.html

when handling signals,

default is - > handle SIGSEGV stop print pass what we need -> handle SIGSEGV nostop noprint pass

https://sourceware.org/gdb/onlinedocs/gdb/Signals.html

Clone this wiki locally