TotalView on BG/Q

TotalView Availability

ALCF does not currently have a general-use TotalView license.    Please contact support if your debugging needs are not met with other ALCF debugging tools.

Instructions below are provided only for use with TotalView licenses granted by special arrangement.

Using TotalView


Add the "+totalview" key to your ~/.softenvrc file (before the @default). E.g.


Then run the command "resoft" (or log out and back in again). This will add the latest installed version of totalview to your PATH.  Please check the output of "softenv" for a list of available keys if you need to run an older version.

Starting your debug session

0.  A sample totalview startup script is available here:


Copy to your directory and modify it as necessary.  There are comments in the sample to help guide you. 

1.  Before submitting your job, check that your DISPLAY is set correctly by running an X11 application (e.g. xterm) from the login node prompt.

2.  Start an interactive Cobalt job:

      # interactive job for 30 min on 32 nodes
      # run in default queue using your default project:

      qsub -I -t 30 -n 32

 3.  When the job runs, you get a shell prompt.

Check that your block is booted:

> wait-boot

Checking status of VST-22040-33151-32
Block state: B (please wait)
Block state: B (please wait)
Block state: B (please wait)
Block state: B (please wait)
Block state: I - READY TO RUN!



4.  Run your

Note: when your job expires, any active runjob will be terminated.  In case of trouble, please check your job status:


An empty output indicates your job is no longer active.


Remote Display Client

If you are using TotalView remotely, the Remote Display Client (RDC) can significantly improve the GUI response.  Download the RDC and install it on your laptop or workstation:


TotalView Release Notes

Detailed information on new features and known problems with the release can be found on the TotalView web site. This link should lead you to a page letting you specify Open/Closed issues, version number, and platform (choose IBM Blue Gene).

Note about Debugging OMP programs

When you compile an OMP application with the IBM XL compilers, note that "-qsmp=omp" also enables automatic parallelization (outside of OMP loops) as well as optimization within loops (even if you use the "-O0" option).    To simplify debugging you may want to use "-qsmp=omp:noauto:noopt".