Native Inspect Manual (H06.03+)

Introducing Native Inspect
Native Inspect Manual—528122-003
1-21
Assessing Your Location After an Event
Table 1-2. Event Handling by Native Inspect
Events Response by Native Inspect
Breakpoint events
Instruction breakpoint
Instruction step
TNS instruction breakpoint
Memory access breakpoint
Displays current code location (PC) and prompts
user for input.
(For TNS instruction breakpoint, displays the current
native code location.)
Entering debug events
Process created in debug
Process puts itself in
debug
Process forced into debug
Process executes embedded
BPT (TNS process)
Creates a debug session with the process (attaches
to the process); makes the process the current
process; displays the current code location and
prompts the user for input.
(For the embedded BPT in a TNS process, displays
the native code location.)
Signal event
Process signalled
Responds according to the preferences set with the
mh command
. Actions include handing control to the
user, printing a message, and forwarding the 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.)
Process death event
Process death
Detaches from the current process and notifies you
that the session was terminated because the current
process died. If Native Inspect is debugging 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.
OSS exec event
OSS exec
Receives process death event and terminates its
session with the current process (the one that called
exec). If the newly created process is running 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.