Allinea Forge (DDT, MAP)¶
Allinea Forge consist of two tools - debugger DDT and profiler MAP.
Allinea DDT is a commercial debugger primarily for debugging parallel MPI or OpenMP programs. It also supports for GPU (CUDA) and Intel Xeon Phi accelerators. DDT provides all the standard debugging features (stack trace, breakpoints, watches, view variables, threads, etc.) for every thread running as a part of your program, or for every process - even if these processes are distributed across a cluster using an MPI implementation.
Allinea MAP is a profiler for C/C++/Fortran HPC codes. It is designed for profiling parallel code, which uses pthreads, OpenMP, or MPI.
License and Limitations for Anselm Users¶
On Anselm users can debug OpenMP or MPI code that runs up to 64 parallel processes. In case of debugging GPU or Xeon Phi accelerated codes, the limit is 8 accelerators. This limitation means that:
- 1 user can debug up to 64 processes, or
- 32 users can debug 2 processes, etc.
In case of debugging on accelerators:
- 1 user can debug on up to 8 accelerators, or
- 8 users can debug on single accelerator.
Compiling Code to Run With DDT¶
Load all necessary modules to compile the code, for example:
$ ml intel $ ml impi **or** ml OpenMPI/X.X.X-icc
Load the Allinea DDT module:
$ ml Forge
Compile the code:
$ mpicc -g -O0 -o test_debug test.c $ mpif90 -g -O0 -o test_debug test.f
Before debugging, you need to compile your code with these flags:
- g: Generates extra debugging information usable by GDB. -g3 includes even more debugging information. This option is available for GNU and Intel C/C++ and Fortran compilers.
- O0: Suppresses all optimizations.
Starting a Job With DDT¶
Be sure to log in with an X window forwarding enabled. This could mean using the -X in the ssh:
$ ssh -X firstname.lastname@example.org
Another options is to access the login node using VNC. See the detailed information on how to use graphic user interface on Anselm.
From the login node, an interactive session with X windows forwarding (-X option) can be started by the following command:
$ qsub -I -X -A NONE-0-0 -q qexp -lselect=1:ncpus=16:mpiprocs=16,walltime=01:00:00
Then launch the debugger with the ddt command followed by the name of the executable to debug:
$ ddt test_debug
A submission window appears with a prefilled path to the executable to debug. Select the number of MPI processors and/or OpenMP threads on which to run, then press run. Command line arguments to a program can be entered to the "Arguments " box.
To start the debugging directly without the submission window, the user can specify the debugging and execution parameters from the command line. For example, the number of MPI processes is set by the "-np 4" option. Skipping the dialog is done by the "-start" option. To see the list of the "ddt" command line parameters, run "ddt --help".
ddt -start -np 4 ./hello_debug_impi
Users can find the original User Guide after loading the DDT module: