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

Figure 1 Native Inspect Runs in Same CPU as Current Process
Starting Native Inspect
You can start or enter Native Inspect in several ways, as follows:
• You can start a process under the control of the debugger, subject to the Debugger Selection
Criteria (using the TACL RUND command or the run -debug command in OSS).
• You can debug a running process (using the TACL DEBUG command).
• A running process can invoke the debugger (calling the PROCESS_DEBUG_ or DEBUG
procedure, by encountering a breakpoint, or as a result of an unhandled signal).
• You can explicitly start Native Inspect from a TACL prompt or from OSS.
These methods are described next.
Starting a Process Under the Control of the Debugger
At the TACL prompt, enter a RUND command, specifying the file name of the TNS/E native object
file you want to debug as follows:
TACL> rund $DISK2.MYSUBVOL.MYFILE
In OSS, enter a run command with the -debug option and specify the file name of the TNS/E
native object file you want to debug as follows:
OSS> run -debug usr/bin/myfile
Native Inspect is automatically run in the same CPU as the process ($DISK2.MYSUBVOL.MYFILE
in the first example) providing that the following conditions are true:
• The target usr/bin/myfile is a TNS/E native program (file code 800).
• You have not set up a Visual Inspect connection to the host.
For more information about when a particular debugger is invoked, see Debugger Selection Criteria
(page 20).
Debugging a Running Process
At the TACL prompt, enter a DEBUG command and specify the name of the TNS/E native process
as follows:
TACL> debug $myproc
Process Debugging Using Native Inspect 19