TotalView Users Guide - CI Wiki

Figure 115: Sorted and
Aggregated Root Window
Using the Process Window
display. In most cases, this is what you want to do as you will not be debugging
these processes or threads.
If you are running TotalView Team, a manager process uses a token in exactly the same
way a user process. For example, if you are running a 32 process MPI job that is
invoked using mpirun, you will need 33 tokens.
� View > Display Exited Threads: Tracking when processes stop and start
executing in a multi-process, multi-threaded enviroment can be challenging.
Selecting this command tells TotalView to display threads after
they’ve exited. While this clutters your display with information about
threads that are no longer executing, it can sometimes be helpful in trying
to track down some problems. You probably don’t want to see these
threads in the listing. However, you can tell TotalView to show them at
anytime. That is, TotalView remembers them so that toggling this command
shows this information.
Using the Process Window
The Process Window (see Figure 116 on page 170) contains the code for the
process or thread that you’re debugging, as well as other related information.
This window contains panes of information. The large scrolling list in
the middle of the Process Window is the Source Pane. (The contents of
these panes are discussed later in this section.)
As you examine the Process Window, notice the following:
� The thread ID shown in the Root Window and in the process’s Threads
Tab with the Tabs Pane is the logical thread ID (TID) assigned by
TotalView and the system-assigned thread ID (SYSTID). On systems such
as HP Alpha Tru64 UNIX, where the TID and SYSTID values are the same,
TotalView displays only the TID value.
TotalView Users Guide: version 8.7 169