dev:debugging
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
dev:debugging [2015/10/02 13:52] – tmueller | dev:debugging [2016/11/02 11:43] – Add parallel debugging, important for oder of mpiecex/valgrind (by Jan W.) 130.60.136.223 | ||
---|---|---|---|
Line 27: | Line 27: | ||
===== valgrind ===== | ===== valgrind ===== | ||
+ | ==== undefined variables ==== | ||
[[ http:// | [[ http:// | ||
Line 55: | Line 56: | ||
</ | </ | ||
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: | ||
+ | |||
+ | < | ||
+ | mpiexec -np 2 valgrind --options cp2k_executable cp2k.inp | ||
+ | </ | ||
===== Memory leak checking ===== | ===== Memory leak checking ===== | ||
Line 70: | Line 93: | ||
===== Compiler warnings ===== | ===== Compiler warnings ===== | ||
- | Unfortunately is the GNU Fortran compiler not on the same level concerning | + | Unfortunately is the GNU Fortran compiler not on the same level concerning warnings as its C/C++ counterparts. Especially the '' |
< | < |
dev/debugging.txt · Last modified: 2020/08/21 10:15 by 127.0.0.1