Start it up with ddt and then click 'Open a core file from a previous run' to debug a program that generated a core file. Start it up with ddt and then click 'Attach to an already running program' if you have a program already running and want to debug that. Debug a program you launch manually (from the command line). Start it up with ddt and then tell it the path to the program by clicking 'Run and Debug a Program', then give the path at the very top of the next window. There are several possible ways to run ddt. $ gcc -g -O0 -fopenmp my_program.c -o my_programįor other debugging flags, or for different compilers, read the Compiler flag page. $ mpif90 -g -O0 my_mpi_program.f90 -o my_mpi_programįor a C OpenMP program, compiled with GCC compilers, this is done like this: For a Fortran 90 MPI program, compiled with GCC compilers, this is done like this: You need to compile your program with the debugging flags enabled (and preferrably with optimization turned off, as that can confuse the results). Use module avail to see the possible compiler toolchains. In this example, I use the compiler toolchain foss/2017a (GCC compilers, OpenMPI, various libraries). You need to load any compilers you will use, as well as DDT itself. There is also a section about X Forwarding in the DDT manual (section 3.12). $ ssh -Y can read more about how to use X11 forwarding on other OS's here. On Linux systems, this is done like this (connecting to HPC2N's Kebnekaise system): If that is not a viable option then you need to enable trusted X11 forwarding. Since DDT has a GUI (Graphical User Interface), it is best used through our ThinLinc setup. Loading the module should set any needed environmental variables as well as the path. You can read more about loading modules on our Accessing software with Lmod page and our Using modules (Lmod) page. Example, loading Arm Forge DDT version 18.2.1 
To see which versions are available and how to load the module. To use the Forge DDT module, add it to your environment.
0 kommentar(er)
