About the Processes & Threads view

The Processes & Threads view displays the state of the processes under debugger control at any given moment. The view updates each time one or more processes moves to another part of the code. If you have set breakpoints, some threads are often stopped at a breakpoint. If all threads are running, the view shows that state.

What the view displays

In Figure 75, the processes and threads are grouped by share group, process state, function, thread ID, and thread state attributes.

  • There are four processes and a total of 12 threads (not all visible).

  • The share group is the set of processes executing the same program, and the executable program name is indicated in its attribute.

    For processes in a native Python debugging session, the label shows the script name instead of the interpreter name. When a share group contains processes running different scripts, each script appears in a separate row, with directory names added when needed to distinguish scripts with the same name.
  • The focus is on thread 1.1 (thread 1 of process 1), as indicated by its bold format.

  • The thread of focus determines the display in the Call Stack, Local Variables, Source, and Data View views.

Figure 75. Processes & Threads tree view

Processes & Threads view in tree view, grouped by share group, process state, function, thread ID, and thread state

The status of processes and threads is highlighted by colored icons for easy identification. The “Mixed” icon () identifies a process whose threads are in different states.

The view displayed in the above figure has these columns:

  • Description: The aggregate groupings that are active for the current program state.

  • #P and #T: The number of processes and threads with a given set of attributes. For example, in Figure 1, three threads from different processes are stopped at a breakpoint in the snore function.

  • Members: A summary of the processes and threads in ptlist format. For example, for the snore function, p3.1, p2.2, p4.2 indicates that thread 1 of process 3 and thread 2 of processes 2 and 4 are stopped at this function. For more information about the ptlist format, see Compressed List Syntax (ptlist) in the dstatus command topic.

Processes or threads may also stop as a result of exit‑related events when stop‑on‑exit is enabled. In these cases, TotalView stops execution immediately before the process or thread terminates. For more information, see Stop execution on process or thread exit (Linux).

To customize the attributes by which the processes and threads are grouped, see Group processes and threads by attribute.

How the view relates to other views

The thread of focus in the Processes & Threads view controls what the other views display. When you change the focus, the Source, Call Stack, Local Variables, and Data View views update to show the source location, call stack, and data values for the selected thread.

Figure 76. Relationships of Processes & Threads, Source, Call Stack, and Data views

Processes & Threads view with the thread of focus in bold, alongside the Source, Call Stack, and Data views that reflect that thread

If you are displaying thread IDs, one line is highlighted in bold (thread ID 8.3 in the previous figure). That line determines the display in the Source view, as well as the Call Stack, Local Variables, and Data View views.

If you are not displaying individual thread IDs, the line representing the aggregate that contains the current thread of focus is bold. If you double-click another line, the display changes to represent the source location, call stack, and data values for that line.

To change the thread of focus, see Change the process or thread of focus.

Related topics

Control how action points work with processes and threads

Action Point Behaviors in the Preferences chapter

Control whether an action point stops a group of processes, a single process (including all its threads), or a single thread.

Controlling an Action Point’s Width