- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -
DDT: Difference between revisions
From HLRS Platforms
Jump to navigationJump to search
(→Usage) |
|||
Line 12: | Line 12: | ||
DDT is available through modules | DDT is available through modules | ||
{{Command|command = | {{Command|command = | ||
module load debugger/ | module load debugger/forge | ||
}} | }} | ||
Line 18: | Line 18: | ||
Do not forget to compile your application with debugging info (<tt>-g</tt> option) | Do not forget to compile your application with debugging info (<tt>-g</tt> option) | ||
}} | }} | ||
== Examples == | == Examples == |
Revision as of 13:19, 31 October 2018
Allinea DDT helps developers fix bugs quickly - from the desktop to the largest supercomputer. The most scalable parallel debugger for debugging MPI and multi-threaded codes, DDT leads the world in performance and usability. |
|
Usage
DDT is available through modules
module load debugger/forge
Note: Do not forget to compile your application with debugging info (-g option)
Examples
starting the application from inside DDT
Get an interactive job and set up the environment within
module load debugger/forge
module load mpi/openmpi
module load mpi/openmpi
Compile your application
mpicc -g your_app.c -o your_app
Start DDT:
ddt your_app
Select the right MPI implementation in the options and run your program.
Hazel Hen special
To debug a program with ddt on Hazel Hen you have to use the Reverse Connection feature. Therefore first launch ddt on a login node:
module load forge
ddt
ddt
Load the forge module in your job script or interactive job and modify your aprun command line therein
module load forge
ddt --connect aprun ...
ddt --connect aprun ...