Native Inspect Manual (H06.03+)

Introducing Native Inspect
Native Inspect Manual—528122-003
1-13
Debugging Multiple Processes
The current process is the process to which all debugging commands apply and the
process for which Native Inspect waits for events.
When Native Inspect has no current process, the command prompt includes the CPU
number and “-2” as the process number. For example:
(eInspect 3,-2):
Abbreviating Native Inspect Commands
You can truncate Native Inspect command names provided that the abbreviation is not
ambiguous. Commonly used command abbreviations are listed as aliases in
Section 3, Syntax of Native Inspect Commands.
For aliases, even ambiguous abbreviations are allowed. For example, the letter s is
defined as an alias for the step command even though many other command names
start with s.
You can test abbreviations by using them as arguments to the help command, help
option.
Debugging Multiple Processes
Native Inspect provides limited support for debugging multiple TNS/E native processes
in both the Guardian and OSS environments. Native Inspect does not provide the
same level of multiprocess debugging capabilities that Inspect has traditionally
provided and that is available on TNS/E systems by debugging with Visual Inspect.
To do multiprocess debugging, either use separate instances of Native Inspect or use
Visual Inspect.
If you use Native Inspect for multiprocess debugging, you can choose either of these
strategies:
•
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.
Two Processes Can Run Under 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.