- 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
m (ddt -> forge) |
|||
| Line 25: | Line 25: | ||
Set up the environment | Set up the environment | ||
{{Command| command = | {{Command| command = | ||
module load debugger/forge | module load debugger/forge<br> | ||
module load mpi/openmpi | module load mpi/openmpi | ||
}} | }} | ||
| Line 54: | Line 54: | ||
ddt --connect aprun ... | ddt --connect aprun ... | ||
}} | }} | ||
== See also == | == See also == | ||
Revision as of 13:17, 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/ddt
Note: Do not forget to compile your application with debugging info (-g option)
Examples
starting the application from inside DDT
Set up the environment
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 ...