TotalView Users Guide - CI Wiki

Naming Lists with Inconsistent Widths
Stepping (Part II): Examples
TotalView lets you create lists that contain more than one width specifier.
This can be very useful, but it can be confusing. Consider the following:
{p2 t7 g3.4}
This list is quite explicit: all of process 2, thread 7, and all processes in the
same group as process 3, thread 4. However, how should TotalView use this
set of processes, groups, and threads?
In most cases, TotalView does what you would expect it to do: it iterates
over the list and acts on each arena. If TotalView cannot interpret an inconsistent
focus, it prints an error message.
Some commands work differently. Some use each arena’s width to determine
the number of threads on which it acts. This is exactly what the dgo
command does. In contrast, the dwhere command creates a call graph for
process-level arenas, and the dstep command runs all threads in the arena
while stepping the TOI. TotalView may wait for threads in multiple processes
for group-level arenas. The command description in the TotalView
Reference Guide points out anything that you need to watch out for.
Stepping (Part II): Examples
The following are examples that use the CLI stepping commands:
� Step a single thread
While the thread runs, no other threads run (except kernel manager threads).
Example: dfocus t dstep
� Step a single thread while the process runs
A single thread runs into or through a critical region.
Example: dfocus p dstep
� Step one thread in each process in the group
While one thread in each process in the share group runs to a goal, the
rest of the threads run freely.
Example: dfocus g dstep
� Step all worker threads in the process while nonworker threads run
Worker threads run through a parallel region in lockstep.
Example: dfocus pW dstep
� Step all workers in the share group
All processes in the share group participate. The nonworker threads run.
Example: dfocus gW dstep
TotalView Users Guide: version 8.7 273