Native Inspect Manual (H06.03+)

Introducing Native Inspect
Native Inspect Manual—528122-003
1-17
Global Debugging
°
Detach from the process from the original Native Inspect.
•
Use the info command with the sessions option to display information about the
processes Native Inspect is currently debugging.
•
You cannot use the automatic display list (expressions that are automatically
displayed by the display command when program execution is suspended) when
you are debugging multiple processes.
Global Debugging
A privileged user (the super ID user) can set one or more global breakpoints
(breakpoints set in code that is shared by multiple processes, such as DLLs). Any
process that encounters the global breakpoint enters the control of Native Inspect.
Such a debug session is defined as global debugging.
Native Inspect Is the Global Debugger
On the TNS/E system, only Native Inspect can do global debugging, and only one
global debugging session can exist in a CPU at any one time. The Native Inspect
instance that sets a global breakpoint is implicitly registered as the global debugger in
that CPU when the first global breakpoint is set, and the Native Inspect instance is
deregistered when the last global breakpoint is removed.
Global debugging is privileged debugging and is a special case of multiprocess
debugging as well (see Debugging Multiple Processes on page 1-13). The super ID
user must use one instance of Native Inspect (that is, the registered global debugger)
to debug all processes that encounter the global breakpoints.
Considerations for Global Debugging
•
Privileged mode must be enabled before you can set breakpoints in or examine
privileged code. The super ID must explicitly enable privileged mode debugging by
entering the priv command.
•
To set a global breakpoint, you must enable privileged debugging and then specify
the -g flag when setting a breakpoint. Global breakpoints are triggered by any
process that executes the code on which the breakpoint is set.
•
Global debugging mode begins when the first global breakpoint is set, and ends
when the last global breakpoint is deleted. While global debugging is in effect, all
other debugging in the CPU is suspended.
•
Native Inspect detects debugging events only when it is waiting. The debugger
can not detect debugging events when prompting the user for input. For this
reason, you should periodically issue the wait command so that Native Inspect can
detect any debugging events that might have occurred. When waiting, you can
press the Break key to redisplay the command prompt.