Starting TotalView
TotalView can debug programs that run in many different computing environments using many different parallel processing modes and systems. This section looks at few of the ways you can start TotalView. See the “TotalView Command Syntax” chapter in the TotalView for HPC Reference Guide for more detailed information.
NOTE >> Starting TotalView with no arguments (just entering
totalview in your shell) launches the Sessions Manager’s Start a Debugging Session dialog,
“Starting a Debugging Session” on page 104.
In most cases, the command for starting TotalView looks like the following:
totalview [ executable [ core-files | recording-file ] ] [ options ]
where executable is the name of the executable file to debug, core-files is the name of one or more core files to examine, and recording-file is the name of a ReplayEngine recording to load.
CLI: totalviewcli [ executable [ core-files | recording-file ] ] [ options ] |
Your environment may require you to start TotalView in another way. For example, if you are debugging an MPI program, you must invoke TotalView on
mpirun. For details, see
“Setting Up Parallel Debugging Sessions” on page 497.
Note that you can use the GUI and the CLI at the same time. Use the
Tools > Command Line command to display the CLI’s window.
NOTE >> Your installation may have its own procedures and guidelines for running TotalView.
The following examples show different ways that you might begin debugging a program: