Native Inspect Manual (H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introducing Native Inspect
- Native Inspect on TNS/E Systems
- Debuggers on NonStop TNS/E Systems
- Origins of Native Inspect
- Process Debugging With Native Inspect
- Debugging Multiple Processes
- Global Debugging
- Debugging TNS Processes
- Snapshot File Analysis
- Debugging DLLs
- Handling Events
- Switching Debuggers (To or From Inspect and Visual Inspect)
- Stopping Native Inspect
- Differences Between Native Inspect and WDB and GDB
- 2 Using Native Inspect
- Quick Start for Inspect Users
- Preparing to Debug Using Native Inspect
- Sample Native Inspect Session
- Start Your Program Under Native Inspect
- Load Symbols
- Determine Compilation-Time Source Name
- Set Source Name Mapping
- Add Current Directory to Source Search Path
- List Source
- Set a Breakpoint on main()
- Continue Execution
- Trace the Stack (Back Trace)
- List Source
- Step Execution (Over Any Function Calls)
- Print a Variable
- Step Execution (Over Any Function Calls)
- Step In to a Called Function
- Set a Memory Access Breakpoint (MAB)
- Trace the Stack (Back Trace)
- List Source
- Continue Listing Source
- Set a Breakpoint on Line 52
- Continue Execution
- Display a Structure
- Enable “pretty” Printing
- Modify a Structure Field
- Terminate Program and Session
- 3 Syntax of Native Inspect Commands
- Categories of Native Inspect Commands
- Syntax of Common Command Elements
- # command
- a command
- add-symbol-file command
- amap command
- attach command
- base command
- break command, tbreak command
- bt command
- can command
- cd command
- commands command
- comment command
- condition command
- continue command
- d command
- delete command
- delete display command
- detach command
- dir command
- disable command
- disable display command
- disassemble command, da command
- display command
- dmab command
- down command, down-silently command
- enable command
- enable display command
- env command
- eq command
- exit command
- fc command
- files command
- finish command
- fn command
- frame command, select-frame command
- help command, help option
- hold command
- i command
- ignore command
- ih command
- info command
- jb command
- jump command
- kill command
- list command
- log command
- ls command
- mab command
- map-source-name command
- mh command
- modify command
- next command, nexti command
- nocstm option
- output command
- print command
- priv command
- ptype command
- pwd command
- quit command
- reg command
- save command
- select-frame command
- set command (environment)
- set command (variable)
- show command
- snapshot command
- source command
- step command, stepi command
- switch command
- symbol command, symbol-file command
- tbreak command
- tj command, tu command
- tn command
- unload-symbol-file command
- until command
- up command, up-silently command
- vector command
- version option
- vq command
- wait command
- whatis command
- x command
- 4 Using Tcl Scripting
- A Command Mapping With Debug and Inspect
- Glossary
- Index
Introducing Native Inspect
Native Inspect Manual—528122-003
1-3
Origins of Native Inspect
Origins of Native Inspect
The Native Inspect application is derived from the WDB command-line debugger
(version 1.3.02). WDB, which is available on HP-UX platforms, is itself derived from
the Free Software Foundation GDB debugger (version 4.17) and from Tool Command
Language (Tcl) 8.0.
Industry Standard, Open Source
The GDB debugger supports many platforms and is a de facto industry-standard
debugger. Like both GDB and WDB, Native Inspect is open source, and much of the
functionality of Native Inspect is the same as that of GDB and WDB.
If you are familiar with GDB or WDB, you should find that Native Inspect is similar in
many ways. Also, consulting open-source documentation about GDB or WDB can
yield information that in many cases applies to Native Inspect as well.
Companion Debugger eGarth
Native Inspect and eGarth are companion debuggers that share syntax in addition to
the same part number (T1237). eGarth is used by HP service providers to examine
CPU dumps and for remote system debugging.
Table 1-1. Three Debuggers on TNS/E Systems
Debugger to Use Type or State You Can Debug Languages Supported
Native Inspect
(on NonStop TNS/E)
(T1237)
- TNS/E native processes (from the
same CPU)
- Snapshots of TNS/E native processes
- Tcl scripting
TNS/E native C/C++,
pTAL
Visual Inspect
(on Windows)
(T7877, T9756,
T9226, T9673)
(the preferred
debugger on TNS/E
systems)
- TNS/E native processes
- TNS/E native snapshots
- Emulated TNS processes
TNS/E native C/C++,
COBOL, pTAL
Inspect
(on NonStop TNS/E)
(T9673)
- Emulated TNS processes on TNS/E
systems (either accelerated with OCA
or interpreted with OCI)
- Snapshots of TNS/R native processes
TNS Fortran,
COBOL,
TAL,
C/C++.
Screen COBOL