Native Inspect Manual (H06.03+)

Introducing Native Inspect
Native Inspect Manual—528122-003
1-15
Using a Separate Instance of Native Inspect for
Each Process
Example of Using Multiple Instances of Native Inspect
You are running Native Inspect in CPU 3 and are debugging the process
$DISK1.MYSUBVOL.MYPROG (CPU,pin=3,301). A second debugging target named
$DISK2.SVOL2.YOURPROG (CPU,pin=3,32) is assigned to your instance of Native
Inspect.
After a debugging event is reported for the new current process, the command prompt
indicates that the current process has changed:
(eInspect 3,301):
< debugging event is reported here >
(eInspect 3,32):
To have a separate Native Inspect instance for each process being debugged, you
need to attach the new process (3,32) to a new Native Inspect instance, and then
detach the process from the original Native Inspect instance:
1. Start a second Native Inspect instance in a different terminal session but running
on the same CPU:
TACL > einspect / cpu 3/
(eInspect 3,-2):
2. Using this new Native Inspect instance, enter an attach command, specifying the
process ID of the process you want to transfer:
(eInspect 3,-2): attach 32
The attach command does not complete until you perform the final step (detach).
3. Using the original Native Inspect instance, enter the detach command, which
releases the new process to the attaching Native Inspect instance and allows the
original process back to its original instance of Native Inspect::
(eInspect 3,32): detach
The display on the new terminal session reveals that the attach has completed,
and process 3,32 is the current process for the new instance of Native Inspect:
(eInspect 3,-2): attach 32
Symbols read in for program loadfile
\PIPPIN.$D0117.TESTS.ODISP3.
Process (3,32) received DS_EVENT_ENTER_DEBUG
(eInspect 3,32):
Now you have two instances of Native Inspect—one attached to each of the two
programs being debugged in CPU 3.