Here we introduce the main views that make up the interface. If a view is not visible, restore it through the Preferences dialog, the Window | Views menu, or the context menu available by right-clicking in the toolbar area.
Central Window
When you first start up NextGen TotalView for HPC, the central window contains either just the Start Page, or the Start Page and a Source view if you started NextGen TotalView for HPC with an executable name argument. This area is reserved for displaying the Start Page, Source views of code, and the Help view.
This central window cannot be closed, and other views cannot be brought into this area as tabs.
Figure 3 – Source View and Start Page
The Source View
Viewing the Program Counter
• In normal debugging mode, the diamond cursor and yellow highlighting identify the Program Counter (PC), i.e. the code location of the debugger. Clicking another line result in a blue highlight, indicating the target line if you use the Run To command. (There is no guarantee that the thread of focus will arrive at that line, of course, if it hits a breakpoint first, or never executes the line.)
• In Replay mode, orange highlighting replaces yellow to identify where ReplayEngine is within the code. The red triangle shows the “Live” location, i.e., the last line executed. Once the PC hits the live location, it shifts from replay mode back to record mode.
Source view actions
• Create breakpoints by clicking on bold line numbers in the gutter.
• See variable information by hovering over a variable name.
• See function information by hovering over function names.
• Search for text strings with the Find function.
If you highlight the function name and select “Navigate to File or Function” from the context menu, the NextGen UI finds and displays the source for the function, if the source is available. If there is more than one source location, the NextGen UI displays the function name as a search in the Lookup view.
Unified Source View Display
The Source view provides a unified view of source-line breakpoints across all image files containing the source file, useful for programs in which the same source file or header file is compiled into multiple image files (e.g., executable and shared library files) used by the process.
Line numbers appear bold where TotalView has identified executable code, i.e., source code lines where the compiler has generated one or more line number symbols in the debug information.
For example, consider debugging a program that launches CUDA code running on a Graphics Processing Unit (GPU). When the host program is first loaded into TotalView, the CUDA threads have not yet launched, so the debugger has no symbol table information yet. Figure 4 shows the Source view before and after a CUDA kernel launch. Before the CUDA threads exist (the left pane), only line 134 has been identified as having executable code.
Figure 4 – Unified source view display
Once the program is running and the CUDA threads have started (the right pane), lines 126, 130, 132, 133, and 134 are bold, so now TotalView has been able to identify line number symbols at those locations.
RELATED TOPICS
Using the Source view to set action points (breakpoints)
