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

Table 6 Event Handling by Native Inspect
Response by Native InspectEvents
Displays current code location (PC) and prompts user for input. (For TNS
code breakpoint, displays the current native code location.)
Breakpoint events
Instruction breakpoint
Instruction step
TNS instruction breakpoint
MAB
Process entered event
Process entered debug event
Creates a debug session with the process (attaches to the process); makes
the process the current process; displays the current code location and
Entering debug events
Process created in debug
Process puts itself in debug
prompts the user for input. (For the embedded breakpoint in a TNS process,
displays the native code location.)
Process forced into debug
Process executes embedded
Breakpoint (TNS process)
Responds according to the preferences set with the mh command. Actions
include handing control to the user, printing a message, and forwarding the
Signal event
Process signalled
signal to the program. (Native Inspect gains control of the current process
at the point of signal generation, before signal handler setup code is invoked.)
Detaches from the current process and notifies you that the session was
terminated because the current process died. If Native Inspect is debugging
Process death event
Process death
one or more additional processes, no current process is designated as the
current process. If there are no other processes and Native Inspect was started
automatically, Native Inspect stops. If you started the debugger, Native
Inspect continues to prompt.
Receives process death event and terminates its session with the current
process (the one that called exec). If the newly created process is running
OSS exec event
OSS exec
in the same CPU as Native Inspect and tdm_execve was used with the
debug option, then Native Inspect receives the process entered debug
event and attaches to the new process.
Switching Between Debuggers (Inspect and Visual Inspect)
If you need to use features that are unique to another debugger, you can switch to a different
debugger as shown in Table 7.
Table 7 Commands for Switching Debuggers
CommandSwitch ToSwitch From
switch command.Inspect or Visual Inspect
(according to Debugger
Native
Inspect
Selection Criteria
(page 20))
Switch to System Debugger command in Visual Inspect (switches to Native
Inspect).
Native InspectVisual Inspect
ADD PROGRAM command in Inspect (receives process from Visual Inspect).Inspect
SELECT DEBUGGER DEBUG command in Inspect (transfers process to
Native Inspect) or you can use the attach command in Native Inspect.
Native InspectInspect
Open Program command in Visual Inspect (receives the process from
Inspect).
Visual Inspect
Breakpoint attributes are not passed between debuggers. When you switch debuggers, Native
Inspect preserves the breakpoints that you have set in the current process, along with any conditions
associated with the breakpoints, including ignore counts or disabling of a breakpoint. When you
switch back to Native Inspect, the breakpoint conditions, ignore-counts, and disable attribute are
reinstated just as they were when you switched control of the process.
Switching Between Debuggers (Inspect and Visual Inspect) 31