Open System Services Programmer's Guide

native processes. The Native Inspect debugger is supported only on TNS/E systems, and supports
debugging of native processes in the OSS and Guardian environments.
The Native Inspect debugger is conceptually similar to the Inspect debuggers and has similar
functionality, but has different syntax and commands. The Native Inspect syntax is based on gdb,
a debugger that is widely used throughout the industry and is familiar to many application
developers.
Both Inspect and Native Inspect are interactive symbolic debuggers. Both provide source-level, or
symbolic, access to a program by allowing you, for example, to refer to a location by the logical
name you have given it in the source code or by the source code line number. The Inspect and
Native Inspect debuggers also provide machine-level access to a program by allowing you to refer
to an item by its absolute or relative address, display and modify machine registers, and display
machine code. However, if you optimize a program, you might need to use low-level debugging
capabilities. On TNS/E systems, Native Inspect provides commands for low-level debugging; on
TNS/R systems, you can use the Debug facility to look at optimized code.
You can start the Inspect or Native Inspect debugger by itself and then run programs within it, or
you can start both the Inspect or Native Inspect debugger and your program at the same time.
Example 8 (page 48) starts the Inspect debugger (on a TNS/R system) or Native Inspect debugger
(on a TNS/E system) by itself, from both the TACL prompt (two examples) and the OSS shell.
Example 8 Starting the Inspect or Native Inspect Debugger by Itself
>RUN INSPECT
or
$ gtacl -p inspect
Example 9 starts the Inspect (on a TNS/R system) or Native Inspect debugger (on a TNS/E system)
and a program to be debugged at the same time, both from the TACL prompt and the OSS shell.
Example 9 Starting the Inspect or Native Inspect Debugger and a Program at the Same Time
> RUND gprog
$ run -debug -inspect=on ossprog
For more information on the G-series Inspect debugger, see the Inspect Manual. If you are familiar
with dbx, a debugger commonly found on UNIX systems, see the Inspect Manual for a table
contrasting dbx and Inspect commands. For more information on the Native Inspect debugger,
see the Native Inspect Manual.
Beginning with the H06.24 and J06.13 RVUs, you have the ability to debug 64-bit OSS programs.
See “64-Bit TNS/E Debugger Support” (page 310) for details.
PC-Based Debuggers
NonStop Development Environment for Eclipse debugging
NSDEE Core with Debugging also includes a separately installed integrated debugger that you
can use to debug TNS/E processes. See “Using the NonStop Development Environment for Eclipse”
(page 52).
Beginning with the H06.24 and J06.13 RVUs, you have the ability to debug 64-bit OSS programs.
See “64-Bit TNS/E Debugger Support” (page 310) for details.
Visual Inspect
Visual Inspect is a PC-based interactive debugging tool that provides a graphical user interface
(GUI) in which you control the debug session and execute debugging commands through pull-down
48 Overview of the OSS Programming Environment