- 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
(Update Remote Connection Example for HAWK) |
(Change order of examples putting HAWK example on first position) |
||
| Line 20: | Line 20: | ||
== Examples == | == Examples == | ||
==== Usage on HAWK ==== | |||
To debug a program with ddt on HAWK you have to use the ''Reverse Connection'' feature. | |||
Therefore first launch ddt on a login node: | |||
{{Command | command = | |||
module load forge<br> | |||
ddt | |||
}} | |||
Then, you have to execute the program you want to debug in a separate shell either via a job script or an interactive job as follows: | |||
Load the forge module in your job script or interactive job and modify your ''mpirun'' command line therein | |||
{{Command | command=module load forge<br> | |||
ddt --connect mpirun ... | |||
}} | |||
After some time a connection request window will pop up in the ddt GUI. Accept the request and you will get the ddt run window to start debugging. | |||
For more information visit the [https://developer.arm.com/docs/101136/latest/arm-forge/connecting-to-a-remote-system ARM documentation]. | |||
=== starting the application from inside DDT === | === starting the application from inside DDT === | ||
| Line 39: | Line 58: | ||
Select the right MPI implementation in the options and run your program. | Select the right MPI implementation in the options and run your program. | ||
== See also == | == See also == | ||
Revision as of 19:12, 8 April 2020
| 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
Examples
Usage on HAWK
To debug a program with ddt on HAWK you have to use the Reverse Connection feature. Therefore first launch ddt on a login node:
ddt
Then, you have to execute the program you want to debug in a separate shell either via a job script or an interactive job as follows:
Load the forge module in your job script or interactive job and modify your mpirun command line therein
ddt --connect mpirun ...
After some time a connection request window will pop up in the ddt GUI. Accept the request and you will get the ddt run window to start debugging.
For more information visit the ARM documentation.
starting the application from inside DDT
Get an interactive job and set up the environment within
module load mpi/openmpi
Compile your application
Start DDT:
Select the right MPI implementation in the options and run your program.