TotalView Users Guide - CI Wiki

Debugging SiCortex Applications
Here is an example of how you would start a Cray XT CNL debugging session:
totalview aprun -a -n4 a.out
TotalView is not able to stop your program before it calls MPI_Init(). While
this is typically at the beginning of main(), the actually location depends on
how you’ve written the program. This means that if you set a breakpoint
before the MPI_Init() call, TotalView ignores it because the statement upon
which you set the breakpoint will have already executed.
Debugging SiCortex Applications
TotalView runs as a cross-debugger within the SiCortex-MIPS Linux environment,
The SiCortex version of TotalView is a 64-bit application and must
run on a x86-64 system running a 64-bit kernel. All debugging must use the
remote features of TotalView.
Features that are not implemented in this version are:
� Memory debugging
� OpenMP
� SHMEM
� PVM
� Debugging 32-bit executables
� Watchpoints
� Compiled EVAL points
Installation Notes
The default location into which the TotalView installer places TotalView
binaries is
/opt/toolworks. In addition, you must use this same path when you install it
into the file system that will be mounted on the MIPS nodes.
For more information on installing TotalView, consult the “TotalView Installation
Guide,” which is located at http://www.totalviewtech.com/Documentation/.
Using TotalView on SiCortex
TotalView must be able to execute a command on the target system from
the development host. By default, this version uses the ssh -x command.
However, we suggest that set up ssh so that lets you execute commands
without requiring a password.
Your program’s executable file must be visible from both the development
host and the target system. Do this by placing the executables in a directory
that is visible on both machines through the same path. Having the
TotalView Reference Guide: version 8.7 147