Creating or Loading a Session
totalview -load_session session_name
Creates a process based on the session values. Sessions that attach to an existing process cannot be loaded this way; use the -pid command line option instead
CLI: totalviewcli dsession -load session_name |
Debugging a Program
totalview executable
Starts TotalView and loads the executable program.
CLI: totalviewcli executable |
If you installed TotalView on a Macintosh using the application bundle, you can drag your program’s executable to the TotalView icon on your desktop.
If you type an executable name, TotalView remembers that name and many of its arguments.
Debugging a Core File
totalview executable corefiles
Starts TotalView and loads the executable program and the corefile core file.
CLI: dattach -c corefiles -e executable |
The corefiles argument represents one or more core files associated with this executable. You can use wild cards in the core file name.
Debugging a Replay Recording Session File
totalview executable ReplayRecordingSessionFile
Starts TotalView and loads the executable program and the ReplayRecordingSessionFile recording session file.
CLI: dattach -c ReplayRecordingSessionFile -e executable |
The ReplayRecordingSessionFile argument represents the replay recording session file associated with this executable.
Passing Arguments to the Program Being Debugged
totalview executable -a args
Starts TotalView and passes all the arguments following the
-a option to the
executable program. When using the
-a option, it must be the last TotalView option on the command line.
CLI: totalviewcli executable -a args |
If you don’t use the
-a option and you want to add arguments after TotalView loads your program, add them either using either the
File > Debug New Program dialog box or use the
Process > Startup command.
CLI: dset ARGS_DEFAULT {value} |
Debugging a Program Running on Another Computer
totalview executable -remote hostname_or_address[:port]
Starts TotalView on your local host and the tvdsvr command (which implements and controls debugging on remote machines) on a remote host. After TotalView begins executing, it loads the program specified by executable for remote debugging. You can specify a host name or a TCP/IP address. If you need to, you can also enter the TCP/IP port number.
CLI: totalviewcli executable
-r hostname_or_address[:port] |
If TotalView fails to automatically load a remote executable, you may need to disable
autolaunching for this connection and manually start the
tvdsvr. (
Autolaunching is the process of automatically launching
tvdsvr processes.) To disable autolaunching, add the
hostname:portnumber suffix to the name entered in the
Debug on Host field of the
File > Debug New Program dialog box. As always, the
portnumber is the TCP/IP port number on which TotalView server is communicating with TotalView. See
"Starting the TotalView Server Manually" for more information.
NOTE >> TotalView Individual does not allow remote debugging.
Debugging an MPI Program
totalview
Method 1: In many cases, you can start an MPI program in much the same way as you would start any other program. However, you need to select A New Parallel program from the Start a Debugging Session dialog box, and enter the MPI version and other information on the parallel program to debug.
mpirun -np count -tv executable
Method 2: The MPI mpirun command starts the TotalView executable pointed to by the TOTALVIEW environment variable. TotalView then starts your program. This program runs using count processes.
Using gnu_debuglink Files
totalview executable
If you have prepared a
gnu_debuglink file, TotalView can access this information. For more information, see
“Using gnu_debuglink Files” within the
Compilers and Platforms chapter of the
TotalView Reference Guide.