dev:debugging
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
dev:debugging [2015/10/02 13:57] – oschuett | dev:debugging [2016/11/02 11:51] – Add OMP_NUM_THREADS and some valgrind options. agloess | ||
---|---|---|---|
Line 27: | Line 27: | ||
===== valgrind ===== | ===== valgrind ===== | ||
+ | ==== undefined variables ==== | ||
[[ http:// | [[ http:// | ||
Line 52: | Line 53: | ||
Run valgrind with | Run valgrind with | ||
< | < | ||
- | valgrind --max-stackframe=2100192 | + | valgrind --max-stackframe=2100192 --leak-check=full --track-origins=yes |
</ | </ | ||
to get the origin of undefined variables in addition to a leak check report. | to get the origin of undefined variables in addition to a leak check report. | ||
+ | |||
+ | |||
+ | ==== understanding memory usage ==== | ||
+ | |||
+ | valgrind also comes with the ' | ||
+ | |||
+ | Rather easy with | ||
+ | |||
+ | < | ||
+ | valgrind --tool=massif ../ | ||
+ | ms_print massif.out.XYZ | ||
+ | </ | ||
+ | |||
+ | The valgrind homepage has [[http:// | ||
+ | |||
+ | ==== valgrind in parallel ==== | ||
+ | |||
+ | valgrind can also be used for debugging parallel code, eg.: | ||
+ | |||
+ | < | ||
+ | mpirun -np 2 -x OMP_NUM_THREADS=2 | ||
+ | </ | ||
===== Memory leak checking ===== | ===== Memory leak checking ===== |
dev/debugging.txt · Last modified: 2020/08/21 10:15 by 127.0.0.1