You copied the Doc URL to your clipboard.

Arm DDT Quick Reference

Workstation or remote interactive sessions

  1. Log in to a terminal session and prepare your environment. Load the environment module for Arm Forge.

    Note

    The name of the environment variable is determined by the system administrator, please check with them for the environment variable you should use for your system.

  2. Either, compile your application (including the -g flag), or locate an appropriately pre-compiled binary. To prepare the code and compile without optimizations, include the -O0 optimization flag on the compile line:

    mpicc -O0 -g myapp.c -o myapp.exe​
    

    Note

    Turning off optimization flags is optional. Optimization flags can re-order the code in unexpected ways and make application debugging less intuitive. If a bug only occurs within an optimized binary, keep the relevant optimizations.

  3. Launch Arm DDT in interactive mode, use the Express Launch syntax:

    ddt mpirun -n 8 ./myapp.exe arg1 arg2
    
  4. Configure any advanced features for your job, such as memory debugging, in the Run dialog.

  5. To start debugging, click Run.

Sessions on an HPC cluster with a job scheduler

To run Arm DDT in interactive mode, you can use the Arm Forge Remote Client or X-forwarding.

Note

For more information on using Arm Forge in non-interactive mode, see the Arm Forge user guide.

  1. Start Arm Remote client, or an X-forwarding session. Either:

    • Arm Remote Client:

      1. Start Arm Remote Client.

      2. If it is your first time using the remote client, add the configuration details for your remote host.

      3. Select the connection from the Remote Launch drop down menu.

    • X-forwarding session:

      1. Connect to the remote host system with X-forwarding enabled:

        ssh -X <remote-host>
        
      2. Prepare your environment. Load the environment module for Arm Forge.

        Note

        The name of the environment variable is determined by the system administrator, please check with them for the environment variable you should use for your system.

  2. On the login node, launch the Arm DDT debugger GUI:

    ddt &
  3. Either, compile your application (including the -g flag), or locate an appropriately pre-compiled binary. To prepare the code and compile without optimizations, include the -O0 optimization flag on the compile line:

    mpicc -O0 -g myapp.c -o myapp.exe​
    

    Note

    Turning off optimization flags is optional. Optimization flags can re-order the code in unexpected ways and make application debugging less intuitive. If a bug only occurs within an optimized binary, keep the relevant optimizations.

  4. Edit your job script to run the Reverse Connect Arm DDT commands ddt --connect:

    ddt --connect mpirun -n 8 ./myapp.exe arg1 arg2​
    
  5. Submit your script

  6. When the GUI displays asking whether you want to accept the incoming connection, click Yes.

  7. Configure any advanced features for your job, such as memory debugging, in the Run dialog.

  8. To start debugging, click Run.

Was this page helpful? Yes No