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

Glossary
G-Series Common Glossary
Glossary-4
signal
A save file can be created through an Inspect or Native Inspect SAVE command at any
time. A save file called a saveabend file can be created by the DMON debug monitor
when a process’s SAVEABEND attribute is set and the process terminates abnormally.
signal. The method by which an environment notifies a process of an event. Signals are
used to notify a process when an error that is not related to input or output has
occurred.
signal handler. A function or procedure that is executed when a specific signal is delivered
to a specific process.
snapshot. In debugging, a disk file that is an image of the process, its data, and its status
at the moment it was saved. Snapshots have file code 130. Snapshots can be
created in a number of ways—for example, the Save command (Native Inspect), the
Save Snapshot command (Visual Inspect), the SAVE command (Inspect), or by the
Snapshot Server INSPSNAP if the SAVEABEND attribute for a process is ON and the
process abends. Native Inspect, Visual Inspect, and Inspect can be used to debug
snapshots. Inspect refers to snapshots as save files. See also save file.
super ID. On HP NonStop systems, a privileged user who can read, write, execute, and
purge all files on the system. The super ID is usually a member of a system-supervisor
group.
The super ID has the set of special permissions called appropriate privileges. In the
Guardian environment, the structured view of the super ID, which is (255, 255), is most
commonly used. In the Open System Services (OSS) environment, the scalar view of
the super ID, which is 65535, is most commonly used.
symbol. (1) The symbolic name of a value, typically a function entry point or a data location.
In the context of loadable libraries, symbols are defined in loadfiles and referenced in
the same or other loadfiles. (2) Within the ServerNet architecture, the nine or more bits
that encode 8-bit data and protocol commands.
symbolic reference. An occurrence in code or data of the value of a symbol. The symbolic
reference is bound (resolved and made usable) by assigning to it the value of a
definition of that symbol. The symbol value is normally the address of a function or
variable named by the symbol. In position-independent code (PIC) loadfiles, symbolic
references occur only in data.
TNS. Fault-tolerant HP NonStop computers that support the HP NonStop operating system
and are based on microcoded complex instruction-set computing (CISC) technology.
TNS systems run the TNS instruction set. Contrast with user code and TNS/E.
TNS mode. The operational environment in which TNS instructions execute by inline
interpretation. See also address space.
TNS/E. Fault-tolerant HP NonStop computers that support the HP NonStop operating
system and are based on the Intel® Itanium® processor. TNS/E systems run the
Itanium instruction set and can run TNS object files by interpretation or after










