Native Inspect Manual (H06.13+, J06.03+)

• When debugging multiple programs, Native Inspect, like Inspect, sets the designated current
process to be the process for which the most recent debugging event has been reported. The
current process is the process to which all commands apply and for which Native Inspect
waits for events.
• Use the vector command to explicitly change the designated current process.
• In a rare situation, two instances of Native Inspect can be running on different CPUs but be
prompting the same home terminal. In this situation, you should do the following:
1. Start another Native Inspect instance on one of the CPUs.
2. Attach the process being debugged in that CPU to the new Native Inspect instance.
3. Detach that process from the original Native Inspect instance.
• Use the info command with the sessions option to display information about the processes
Native Inspect is currently debugging.
• You cannot use the automatic display list (expressions that are automatically displayed by the
display command when program execution is suspended) when you are debugging multiple
processes.
Identifying 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 as follows:
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/
Each terminal session defines 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.
Remember that while you are debugging this second process on a different terminal session,
the home terminal for the process itself remains unchanged, and the process might attempt to
prompt or output to its home terminal, causing more contention. Because of this potential
problem, use Visual Inspect as the preferred debugger for multiprocess debugging.
2. Transfer the current process to the new Native Inspect instance as follows:
a. From the new Native Inspect instance, enter the attach command.
b. From the original Native Inspect instance, release the current process (the newer debugging
target) by entering the detach command.
Debugging Multiple Processes 25