Native Inspect Manual (H06.04+)

Introducing Native Inspect
Native Inspect Manual—528122-005
1-9
Debugger Selection Criteria
Invoking the Debugger From a Running Process
Native Inspect is automatically started by the NonStop operating system when a
debugger is required for any of the following reasons:
•
TNS/E native process code calls the PROCESS_DEBUG_ or DEBUG procedure.
•
A TNS/E native process encounters a breakpoint set by a prior debugging session.
•
The user of another debugger switches to Native Inspect.
When a running process invokes a debugger, the operating system automatically
selects a debugger according to the debugger options you set (INSPECT ON or OFF)
in addition to the process type (TNS versus TNS/E) and the availability of a connection
to Visual Inspect, which is the preferred debugger on TNS/E systems.
Debugger Selection Criteria
Two figures illustrate the criteria that are evaluated during debugger selection:
•
Figure 1-2, Debugger Selection for a TNS/E Native Process, on page 1-10
•
Figure 1-3, Debugger Selection for a TNS Process Running on TNS/E, on
page 1-11
In both Figure 1-2 and Figure 1-3, debugger selection criteria are defined as follows:
INSPECT attribute on?
INSPECT is set to ON for the process you will debug
(set with TACL, the linker, or the RUN[D] command).
Visual Inspect session? You have started Visual Inspect and have connected to
the TNS/E host on which the process to be debugged
will run. The user ID of the process must match the
user ID that was used to log on to Visual Inspect.
Inspect available? The Inspect subsystem (IMON, DMON, $DMnn) is
running, and the Inspect command-line interface is
available.