This glossary defines terms specific to TotalView.

A breakpoint. TotalView action points include standard breakpoints, watchpoints, eval points, and barriers.

A unique integer ID associated with an action point.

The set of process and threads that are affected by the command. For most commands, this is identical to the target P/T set, but in some cases it might include additional threads. (See p/t (process/thread) set for more information.)

The CLI compresses output from multiple threads when they would be identical except for the P/T identifier.

A specifier that indicates the processes, threads, and groups upon which a command executes. Arena specifiers are p (process), t (thread), g (group), d (default), and a (all).

A subsection of an array, which is expressed in terms of an upper bound, a lower bound, and a stride. Displaying a slice of an array can be useful when you are working with very large arrays.

When a process begins executing on a remote computer, TotalView can also launch a tvdsvr (TotalView Debugger Server) process on the computer that will send debugging information back to the TotalView process that you are interacting with.

TotalView detects the many processes that parallel and distributed programs run in, and attaches to them automatically so you don’t have to attach to them manually. If the process is on a remote computer, automatic process acquisition starts the -TotalView Debugger Server (tvdsvr).

An action point specifying that processes reaching a particular location in the source code should stop and wait for other processes to catch up.

A debugger-maintained list that stores copies of the most recent commands issued by the user.

A breakpoint containing an expression. If the expression evaluates to true, program stops. TotalView does not have conditional breakpoints. Instead, you must explicitly tell TotalView to end execution by using the $stop directive.

All the processes that a program creates. These processes can be local or remote. If your program uses processes that it did not create, TotalView places them in separate control groups. For example, a client/­server program has two distinct executables that run independently of one another. Each would be in a separate control group. In contrast, processes created by the fork() function are in the same control group.

See tvdsvr process.

Information that TotalView or the CLI maintains to interpret and respond to user commands. This includes debugger modes, user-defined commands, and debugger variables.

Debugger ID. The ID used for processes.

A point in the program where TotalView evaluates a code fragment without stopping the execution of the program.

A part of TotalView that evaluates C, C++, and Fortran expressions. An expression consists of symbols (possibly qualified), constants, and operators, arranged in the syntax of a source language. Not all Fortran 90, C, and C++ operators are supported.

The set of groups, processes, and threads upon which a CLI command acts. The current focus is indicated in the CLI prompt (if you’re using the default prompt).

The TotalView group ID.

The group of interest. This is the group that TotalView uses when it is trying to determine what to step, stop, and so on.

When TotalView starts processes, it places related processes in families. These families are called “groups.”

The primary group that is affected by a command. This is the group that TotalView uses when it is trying to determine what to step, stop, and so on.

The Heap Interposition Agent, used when memory debugging. The HIA intercepts calls to heap library functions that allocate and deallocate memory by using the malloc() and free() functions and related functions such as calloc() and realloc(). In most cases, the HIA is loaded automatically when your program starts. For some platforms, however, the HIA needs to be explicitly linked to your application. See Linking Your Application with the Agent in Debugging Problems with MemoryScape.

The computer on which TotalView is running.

The process created as part of a load operation, or that already existed in the runtime environment and was attached by TotalView or the CLI.

An optional file that establishes initial settings for debugger state variables, user-defined commands, and any commands that should be executed whenever TotalView or the CLI is invoked. Must be called .tvdrc.

All threads that are at the same PC (program counter). This group is a subset of a workers group. A lockstep group only exists for stopped threads. All threads in the lockstep group are also in a workers group. By definition, all members of a lockstep group are in the same workers group. That is, a lockstep group cannot have members in more than one workers group or more than one control group.

A thread created by the operating system. In most cases, you do not want to manage or examine manager threads.

The action of debugging a program that is running on the same machine as TotalView.

Depending on the context, this is either the process ID or the program ID. In most cases, this is the process ID.

The process of interest. This is the process that TotalView uses when it is trying to determine what to step, stop, and so on.

A group of processes associated with a multi-process program. A process group includes program control groups and share groups.

A unique integer ID associated with a particular process and thread.

The primary process that TotalView uses when it is trying to determine what to step, stop, and so on.

A group of processes that includes the parent process and all related processes. A program control group includes children that were forked (processes that share the same source code as the parent), and children that were forked with a subsequent call to the execve() function (processes that don’t share the same source code as the parent). Contrast this with share group.

A program occurrence that is being monitored by TotalView or the CLI, such as a breakpoint.

The set of threads drawn from all threads in all processes of the target program.

The ID assigned by the Posix pthreads package. If this differs from the system TID, it is a pointer value that points to the pthread ID.

The set of processes and threads that must be held before a barrier can be satisfied.

A condition that indicates that all processes or threads in a group have reached a barrier. Prior to this event, all executing processes and threads are either running because they have not yet hit the barrier, or are being held at the barrier because not all of the processes or threads have reached it. After the barrier is satisfied, the held processes or threads are released, which means they can be run. Prior to this event, they could not run.

A form of remote debugging where TotalView and the tvdsvr communicate over a serial line.

A thread whose purpose is to service or manage other threads. For example, queue managers and print spoolers are service threads. There are two kinds of service threads: those created by the operating system or runtime system and those created by your program.

All the processes in a control group that share the same code. In most cases, your program has more than one share group. Share groups, like control groups, can be local or remote.

A TotalView procedure that individually launches tvdsvr processes.

A subsection of an array, which is expressed in terms of a lower bound, upper bound, and stride. Displaying a slice of an array can be useful when you are working with very large arrays.

A set of threads that TotalView stops after an action point -triggers.

The interval between array elements in a slice and the order in which TotalView displays these elements. If the stride is 1, TotalView displays every element between the lower bound and upper bound of the slice. If the stride is 2, TotalView displays every other element. If the stride is -1, TotalView displays every element between the upper bound and lower bound (reverse order).

The computer on which the process to be debugged is running.

The target set for those occasions when operations can only be applied to entire processes, not to individual threads in a process.

The executing program that is the target of debugger operations.

The set of processes and threads on which a CLI command acts.

The primary thread affected by a command.

The thread ID. On some systems (such as AIX where the threads have no obvious meaning), TotalView uses its own IDs.

The set of threads that can trigger an action point (that is, the threads upon which the action point was defined).

The effect during execution when program operations cause an event to occur (such as arriving at a breakpoint).

The TotalView Debugger Server process, which facilitates remote debugging by running on the same machine as the executable and communicating with TotalView over a TCP/IP port or serial line.

Abbreviated as TTF. A TotalView subsystem that allows you to change the way information appears. For example, an STL vector can appear as an array.

A thread created by your program.

An action point that stops execution when the value of a memory location changes.

A thread in a workers group. These are threads created by your program that perform the task for which you’ve written the program.

All the worker threads in a control group. Worker threads can reside in more than one share group.