valgrind

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
valgrind [2018/01/08 14:09]
doeringn [On Mogon] 		valgrind [2019/05/22 10:10]
meesters removed
Line 11: Line 11:
 ===== On Mogon ===== ===== On Mogon =====
  
-On Mogon, valgrind is compiled on the a*-nodes and available as the module ''debugger/Valgrind/3.13.0-foss-2016a''((as of 23. Nov. 2017)).+On Mogon, valgrind is compiled on the a*-nodes and available as the module ''debugger/Valgrind/<version>-<toolchain>''.
  
 ===== Things to consider when using Valgrind ===== ===== Things to consider when using Valgrind =====
Line 29: Line 29:
 Imaging you submit a job like: Imaging you submit a job like:
 <code bash> <code bash>
- bsub -n 1 -app Reserve1800M -q short -W 300 valgrind --tool=callgrind cmd [args]+ srun -p short -A <your account> -n 1 --mem 1800M -t 300 valgrind [other valgrind args] --tool=callgrind <path/to/cmd> [args]
 </code> </code>
 where ''cmd'' is the program to profile with its optional arguments (''args''). where ''cmd'' is the program to profile with its optional arguments (''args'').
  
-This will produce an output file (e.g. ''callgrind.out.44289'') which you can further analyze on the command line:+This will produce an output file (e.g. ''callgrind.out.44289'', with 44289 being the PID of the process) which you can further analyze on the command line:
 <code bash> <code bash>
 callgrind_annotate --auto=yes callgrind.out.44289 |less callgrind_annotate --auto=yes callgrind.out.44289 |less