dptsets

Shows the status of processes and threads

Format: 

dptsets [ ptset_array ] ...

Arguments: 

ptset_array

An optional array that indicates the P/T sets to show. An element of the array can be a number or it can be a more complicated P/T expression. (For more information, see “Using P/T Set Operators” in Chapter 12 of the TotalView User Guide.)

Description: 

The dptsets command shows the status of each process and thread in a Tcl array of P/T expressions. These array elements are P/T expressions (see Chapter 12 of the TotalView User Guide), and the elements’ array indices are strings that label each element's section in the output.

If you do not use the optional ptset_array argument, the CLI supplies a default array that contains all P/T set designators: error, existent, held, running, stopped, unheld, and watchpoint.

Examples: 

The following example displays information about processes and threads in the current focus:

d.1<> dptsets

unheld:

1: 808694 Stopped [fork_loopSGI]

1.1: 808694.1 Stopped PC=0x0d9cae64

1.2: 808694.2 Stopped PC=0x0d9cae64

1.3: 808694.3 Stopped PC=0x0d9cae64

1.4: 808694.4 Stopped PC=0x0d9cae64

existent:

1: 808694 Stopped [fork_loopSGI]

1.1: 808694.1 Stopped PC=0x0d9cae64

1.2: 808694.2 Stopped PC=0x0d9cae64

1.3: 808694.3 Stopped PC=0x0d9cae64

1.4: 808694.4 Stopped PC=0x0d9cae64

watchpoint:

running:

held:

error:

stopped:
1: 808694 Stopped [fork_loopSGI]

1.1: 808694.1 Stopped PC=0x0d9cae64

1.2: 808694.2 Stopped PC=0x0d9cae64

1.3: 808694.3 Stopped PC=0x0d9cae64

1.4: 808694.4 Stopped PC=0x0d9cae64

...

The following example creates a two-element P/T set array, and then displays the results. Notice the labels in this example.

d1.<> set set_info(0) breakpoint(1)

breakpoint(1)

d1.<> set set_info(1) stopped(1)

stopped(1)

d1.<> dptsets set_info

0:

1: 892484 Breakpoint [arraySGI]

1.1: 892484.1 Breakpoint PC=0x10001544, [array.F#81]

 

1:

1: 892484 Breakpoint [arraySGI]

1.1: 892484.1 Breakpoint PC=0x10001544, [array.F#81]

The array index to set_info becomes a label identifying the type of information being displayed. In contrast, the information within parentheses in the breakpoint and stopped functions identifies the arena for which the function returns information.

If you use a number as an array index, you might not remember what is being printed. The following very similar example shows a better way to use these array indices:

d1.<> set set_info(my_breakpoints) breakpoint(1)

breakpoint(1)

d1.<> set set_info(my_stopped) stopped(1)

stopped(1)

d1.<> dptsets set_info

my_stopped:

1: 882547 Breakpoint [arraysSGI]

1.1: 882547.1 Breakpoint PC=0x10001544, [arrays.F#81]

 

my_breakpoints:

1: 882547 Breakpoint [arraysSGI]

1.1: 882547.1 Breakpoint PC=0x10001544, [arrays.F#81]

The following commands also create a two-element array. This example differs in that the second element is the difference between three P/T sets.

d.1<> set mystat(system) a-gW

d.1<> set mystat(reallystopped) \

stopped(a)-breakpoint(a)-watchpoint(a)

d.1<> dptsets t mystat

system:

Threads in process 1 [regress/fork_loop]:

1.-1: 21587.[-1] Running PC=0x3ff805c6998

1.-2: 21587.[-2] Running PC=0x3ff805c669c

...

Threads in process 2 [regress/fork_loop.1]:

2.-1: 15224.[-1] Stopped PC=0x3ff805c6998

2.-2: 15224.[-2] Stopped PC=0x3ff805c669c

...

 

reallystopped:

2.2 224.2 Stopped PC=0x3ff800d5758

2.-1 5224.[-1] Stopped PC=0x3ff805c6998

2.-2: 15224.[-2] Stopped PC=0x3ff805c669c

...