Native Inspect Manual (H06.04+)

Introducing Native Inspect
Native Inspect Manual—528122-005
1-13
Abbreviating Native Inspect Commands
Reading the eInspect Custom File
As Native Inspect initializes, it reads the contents of its custom file, named EINSCSTM,
located in your logon default $vol.subvol on the TNS/E host. This file can contain
any Native Inspect commands that you want to take effect during initialization. For
example, you might establish your typical debugging environment by including a
number of set commands (see set command (environment)).
Command Prompt Indicates the Current Process
After Native Inspect initializes, it displays its command prompt. The Native Inspect
prompt contains the name eInspect and the CPU number and process number of the
current process or debugging target.
For example, this prompt indicates that process 0,301 is the current process:
(eInspect 0,301):
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 4,
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 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.
Multiprocess debugging is easiest using either Visual Inspect or separate instances of
Native Inspect.
If you use Native Inspect for multiprocess debugging, you can choose either of these
strategies: