Native Inspect Manual (H06.07+)

Introducing Native Inspect

Native Inspect Manual—528122-006

1-4

Not Part of the Inspect Subsystem

Because Native Inspect originated in the UNIX world, Native Inspect is not part of the

Inspect subsystem. Both Inspect and Visual Inspect, however, are part of the Inspect

subsystem.

Documentation for Native Inspect

Native Inspect-Specific

•

This manual: Native Inspect Manual

•

Native Inspect online help (see the help command, help option on page 4-35)

Related Documents

•

Hewlett-Packard home page for WDB:

http://www.hp.com/go/WDB

•

User manual for GDB version 4.17, by Richard M. Stallman and Roland H. Pesch:

http://www.objsw.com/docs/gdb_toc.html

•

Current GDB documentation from Red Hat:

http://sources.redhat.com/gdb/

Comparing Native Inspect to Debug

Native Inspect takes the place of Debug as the low-level default process debugger on

TNS/E systems. Therefore, Native Inspect is the debugger invoked if Visual Inspect

(the preferred debugger on TNS/E systems) is not available (for example., if no

connection exists to a Windows client) or if the INSPECT parameter is set to OFF.

Debugger selection criteria are shown in Figure 1-2, Debugger Selection for a TNS/E

Native Process, on page 1-10 and in Figure 1-3, Debugger Selection for a TNS

Process Running on TNS/E, on page 1-11.

Debug was an integral part of the operating system on previous NonStop platforms.

On TNS/E, Native Inspect is a separate licensed object file

($SYSTEM.SYSnn.EINSPECT), but still fulfills the role of built-in debugger. Whereas

Debug executed in the context of the process being debugged, Native Inspect

executes as a separate process in the same CPU as the process being debugged.

Running as a separate process reduces the chances of the debugger affecting target

process behavior.

Some Commands Are Debug-Compatible

Although Native Inspect is completely different in form from Debug, Native Inspect

provides many Debug-compatible commands, such as a, base, fn, ih, and mh. For a