- 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
(Undo revision 3353 by Hpcjgrac (talk))
(7 intermediate revisions by 2 users not shown)
Line 12: Line 12:
DDT is available through modules
DDT is available through modules
{{Command|command =
{{Command|command =
module load debugger/ddt
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 ==
=== starting the application from inside DDT ===
=== starting the application from inside DDT ===


Set up the environment
Get an interactive job and set up the environment within
{{Command| command =
{{Command| command =
module load debugger/ddt
module load debugger/forge<br>
module load mpi/openmpi
module load mpi/openmpi
}}
}}
Line 39: Line 38:
}}
}}


Select the right MPI Implementation in the Options and run your program.
Select the right MPI implementation in the options and run your program.
 
==== Nec Nehalem Cluster special ====
 
If you want to debug a parallel Program using Open MPI with DDT on the NEC Nehalem Cluster select 'OpenMPI (Compatibility)' as the desired MPI Implementation.
 


==== Cray XT5m special ====
==== Hazel Hen special ====


If your program does IO take care to start an interactive session from the correct directory.
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:
==== Hermit special ====
{{Command | command =
 
module load forge<br>
Currently the usage of DDT on Hermit is only supported within an interactive job.
ddt
{{Command| command =
qsub -IX [other job options]
}}
}}


To start your program under the control of DDT first load the ddt module
Load the forge module in your job script or interactive job and modify your ''aprun'' command line therein
{{Command | command =  
{{Command | command =module load forge<br>
module load ddt
ddt --connect aprun ...
ddt your_app
}}
}}
{{Note| text =
Ensure that you select "Cray XT/XE/XK (MPI/shmem)" as your MPI implementation and that the job is not submitted via the queuing system.
}}
<!-- === attaching to an already running application === -->


== See also ==
== See also ==

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.
Developer: Allinea
Platforms: NEC Nehalem Cluster
Category: Debugger
License: Commercial
Website: Allinea homepage


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


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


Load the forge module in your job script or interactive job and modify your aprun command line therein

module load forge
ddt --connect aprun ...


See also

External links