Start TotalView and create a debugging session
You can start TotalView in two primary ways:
-
with no arguments to launch the Start Page
-
with arguments to skip the Start Page and open the UI with the program loaded and ready to debug
On this page:
Start TotalView without arguments
You can start TotalView without arguments, as follows:
totalview
This opens TotalView displaying the Start Page, from which you can launch the Sessions Editor.
Using the Start Page to launch the Session Editor is a convenient way to load a program into TotalView. After you configure a debugging session using the Sessions Editor, the settings are saved under Recent Sessions so you can access them later.
From this page you launch the Session Editor to:
-
Specify a program to debug — Debug a Program
-
Specify a native Python program to debug — Debug a Python Program
-
Specify a parallel program to debug — Debug a Parallel Program
-
Start debugging a running program — Attach to Process
-
Specify a core file to debug or a ReplayEngine recording file to load — Load Core or Replay Recording File
-
Restart a previously defined session — example: tx_arrays_array_config
-
Run the TotalView UI on a local machine while accessing the TotalView engine on a remote node — Listen for Reverse Connections
-
Remotely debug a program — Launch Remote Debugger
-
Open the support web page — Support
Start TotalView with arguments to load a program
Load a program into TotalView by entering:
totalview executable_name [ argument argument ... ]
where executable_name is the executable of the program you want to debug, followed by any arguments the program takes. This opens the TotalView UI with the program loaded and ready to debug.
Figure 10 shows the Source view for the program and the Processes & Threads view. These are just two of several available views.
Figure 10. Starting TotalView with an executable name
For the syntax to launch TotalView to a native Python debugging session, see Launch single-process Python programs and Launch parallel Python programs.