Native Inspect Manual (H06.04+)

Introducing Native Inspect
Native Inspect Manual—528122-005
1-14
Debugging Two Processes With One Instance of
Native Inspect
•
Use a separate Native Inspect instance for each process so that you are issuing
debug requests from separate terminal sessions.
•
Use one instance of Native Inspect for all processes so that one process is the
current process and the other processes are in the background.
Debugging Two Processes With One Instance of Native Inspect
Suppose that you are running Native Inspect and are debugging a process (this is the
“current process” of the debugger, or the debugging target). Another process will
automatically be given to your existing instance of Native Inspect if a TNS/E native
process causes a debugger to be invoked, and the TNS/E process is running in the
same CPU and has the same user ID as your current process (or if you are using the
super ID).
Two processes are then under the control of one instance of Native Inspect. See
Example of Using Multiple Instances of Native Inspect on page 1-15.
Native Inspect Informs You of Additional Processes
Native Inspect informs you that it has control of another debugging target after you do
one of the following:
•
Enter a process-control command (which causes Native Inspect to wait for events),
such as the continue command, finish command, next command, nexti command,
step command, stepi command, and until command.
•
Enter the wait command.
•
Press the Break key.
In this case, when you use Native Inspect to debug multiple processes, the current
process is the one for which the most recent debugging event has been reported.
Using a Separate Instance of Native Inspect for Each Process
If you have two processes under the control of one instance of Native Inspect, you can
transfer one of the processes to another instance of Native Inspect as follows:
1. Start a new Native Inspect instance on a different terminal session, specifying the
same CPU as the original instance of Native Inspect:
Each OutsideView or TelNet terminal session is a different “home terminal.”
However, you can transfer a process to a Native Inspect instance on a different
terminal session as long as the new instance of Native Inspect is running in the
same CPU and under the same user ID.
TACL> status *, term
Process Pri PFR %WT Userid Program file Hometerm
$Z160 3,301 123 R 000 8,12 $SYSTEM.SYS00.EINSPECT $ZP1.#PHF
TACL> einspect /cpu 3/