- 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
m (ddt -> forge) |
|||
| (8 intermediate revisions by the same user not shown) | |||
| Line 12: | Line 12: | ||
DDT is available through modules | DDT is available through modules | ||
{{Command|command = | {{Command|command = | ||
module load | module load 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 == | ||
=== | ==== Usage on HAWK ==== | ||
To debug a program with ddt on HAWK you have to use the ''Reverse Connection'' feature. | |||
To debug a program with ddt on | |||
Therefore first launch ddt on a login node: | Therefore first launch ddt on a login node: | ||
{{Command | command = | {{Command | command = | ||
| Line 50: | Line 29: | ||
}} | }} | ||
Load the forge module in your job script or interactive job and modify your '' | 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: | ||
{{Command | command =module load forge<br> | Load the forge module in your job script or interactive job and modify your ''mpirun'' command line therein | ||
ddt --connect | {{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 === | |||
= | Get an interactive job (with X forwarding) and set up the environment within | ||
{{Command| command = | |||
module load forge<br> | |||
module load openmpi | |||
}} | |||
Start DDT: | |||
{{Command| command = | |||
ddt your_app | |||
}} | |||
Select the right MPI implementation in the options and run your program. | |||
== See also == | == See also == | ||
Latest revision as of 14:52, 25 April 2023
| 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 (with X forwarding) and set up the environment within
module load openmpi
Start DDT:
Select the right MPI implementation in the options and run your program.