C/C++ Programmer's Guide (G06.27+, H06.03+)

Running and Debugging C and C++ Programs
HP C/C++ Programmer’s Guide for NonStop Systems—429301-010
19-13
Native Inspect
Native Inspect
Native Inspect is a symbolic debugger for NonStop NS-series systems and is based
upon the open-source GNU dbg utility. Native Inspect provides both machine-level and
source-level process debugging.
If you compile your TNS/E native program using the SYMBOLS pragma, you can use
the source-level commands to access your process in terms of variables, functions,
statements, and other source-level entities. In addition, if you have a thorough
understanding of the HP NonStop architecture, you can use the machine-level
commands to access registers, code and data segments, stack, and other machine-
level entities.
If you compile your program using the SAVEABEND pragma, the system automatically
creates a save file, or snapshot, of your running program if it terminates abnormally.
You can use Native Inspect to examine the save file and diagnose the cause of the
abnormal termination.
For more details about Native Inspect, see the Native Inspect Manual.
Visual Inspect Symbolic Debugger
Visual Inspect is an optional HP PC-based (GUI) symbolic debugger designed to work
in complex distributed environments. Visual Inspect provides only source-level
debugging for servers executing in the NonStop environments.
Visual Inspect is a client-server application; the server runs on the HP NonStop
platform, and the client runs on the PC. Visual Inspect is also integrated into the HP
Enterprise Tool Kit on the PC.
As when using the Inspect or Native Inspect symbolic debuggers, you must use the
SYMBOLS pragma to enable the inclusion of symbol information in your object file and
you should not strip the executable file using a linker or the strip utility. You can also
use the SAVEABEND pragma to create a save file if your program terminates
abnormally.
For more details about enabling and using Visual Inspect, see the online help for
Visual Inspect.