Using the Root Window
The Root Window appears when you start TotalView.
If you type a program name immediately after the totalview command, TotalView also opens a Process Window with the program’s source code. If you do not enter a program name when starting TotalView, TotalView displays its File > New Debugging Session dialog box. Use this dialog box to select the type of debug session you wish to configure. The Root Window displays a list of aggregated processes and threads — instead of displaying one line per each process or thread, it groups them by common properties that you can configure. This provides a considerable performance boost when scaling to thousands — or more — threads or processes. The status of processes and threads is highlighted by colored icons for easy identification.
NOTE: To display the Root Window from versions prior to TotalView 8.15.0, see Using the Old Root Window. The old Root Window, however, does not perform as well for high-scale programs. See Chapter 27, Scalability in HPC Computing Environments .
Figure 62 shows the Root Window for an executing multi-threaded, multi-process program.
 |
The Root Window groups threads and processes under common properties. The initial default view groups the display by control group, process state, function, and thread ID. You can regroup and reduce the display in a number of ways, based on either process or thread properties, as described in Table 1.
Process | Property Level | Description |
|---|---|---|
Control Group | Process | Control group of the processes in your job. Processes in the same job are placed in the same control group by default. If there is only one control group in the debug session, this property is omitted from the display. |
Share Group | Process | Share group of the processes within a control group. Processes that are running the same main executable are placed in the same share group by default. |
Hostname | Process | The hostname or IP address where the process is running. |
Process State | Process | The process execution state, e.g., Nonexistent, Running, Stopped, Breakpoint, Watchpoint, etc. The process execution state derives from the execution state of the threads it contains. |
Thread State | Thread | The thread execution state, e.g., Running, Stopped, Breakpoint, Watchpoint, etc. |
Function | Thread | The function name of the location of the stopped thread. Displays the function name or "<unknown address>" if the thread is running or the function name is not known. |
Source Line | Thread | The function name of the location of the stopped thread. Displays the source file name and line number or "<unknown line>" if the thread is running or the source line is not known. |
PC | Thread | The PC of the location of the stopped thread. Displays the program counter value or "<unknown address>" if the thread is running. |
Action Point ID | Thread | The action point (breakpoint or watchpoint) ID of the location of the stopped thread. Displays "Break (ID)", where ID is the action point ID or "none" if the thread is not stopped at an action point. |
Stop Reason | Thread | If stopped, the reason, for example due to a breakpoint or barrier point. |
Process ID | Process | The debugger process ID (dpid) of the process. Displays dpid. |
Thread ID | Thread | The dpid and debugger thread ID (dtid) of the thread. Displays dpid dtid. |
Process Held | Process | Indicates that a process is being held at a barrierpoint. |
Thread Held | Thread | Indicates that a thread is being held at a barrierpoint. |
Replay Mode | Process | Indicates that the process is in record mode. |
System TID | Thread | The user thread ID (user TID) if it exists. Otherwise, the system kernel ID (Kernel TID). |
User_TID/Kernel_TID | Thread | User thread ID / Kernel thread ID |
Thread Name | Thread | The name of the thread, if set. If unset, “unnamed” is displayed. |
The various properties here are either process or thread-level, which determines the kind of ptlist displayed in the Members column: the members of process-level properties are processes, and the members of thread-level properties are threads.
You can also use the CLI’s dstatus command’s -group_by switch for additional reduction options.
The CLI’s dstatus command’s -group_by switch | dstatus in the Reference Guide |
