Native Inspect Manual (H06.03+)

Introducing Native Inspect
Native Inspect Manual—528122-003
1-8
Starting Native Inspect
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:
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:
OSS> run -debug pathname
Native Inspect is automatically run in the same CPU as the process
($DISK2.MYSUBVOL.MYFILE in the first example)as long providing that:
•
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 on page 1-9.
Debugging a Running Process
At the TACL prompt, enter a DEBUG command and specify the name of the TNS/E
native process:
TACL> debug $myproc
This command starts Native Inspect on the home terminal of the process $myproc.
You can optionally specify a home terminal on which you want Native Inspect to run, as
follows:
TACL> debug $myproc, term $ztn10.#pthef
In OSS, enter a DEBUG command that includes the CPU and process numbers of the
process you want to debug:
OSS> debug 5,135, term $myterm
Native Inspect gains control of the running process subject to the NonStop debugging
rules (described in Debugger Selection Criteria on page 1-9).
For example, if a process is executing privileged code, the process must return to
nonprivileged code before a nonprivileged debug request completes. If you are logged
on as the super ID (255,255), you can enter the DEBUGNOW command, which
immediately gives you access to the specified process, even if it is running privileged
code.