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-14
Native Inspect Informs You of Additional Processes
Native Inspect Informs You of Additional Processes
Native Inspect informs you that it has control of another debugging target after you do
one of the following:
•
Enter a process-control command (which causes Native Inspect to wait for events),
such as the continue command, finish command, next command, nexti command,
step command, stepi command, and until command.
•
Enter the wait command.
•
Press the Break key.
In this case, when you use Native Inspect to debug multiple processes, the current
process is the one for which the most recent debugging event has been reported.
Using a Separate Instance of Native Inspect for Each Process
If you have two processes under the control of one instance of Native Inspect, you can
transfer one of the processes to another instance of Native Inspect as follows:
1. Start a new Native Inspect instance on a different terminal session, specifying the
same CPU as the original instance of Native Inspect:
Each OutsideView or TelNet terminal session is a different “home terminal.”
However, you can transfer a process to a Native Inspect instance on a different
terminal session as long as the new instance of Native Inspect is running in the
same CPU and under the same user ID.
Remember that while you are debugging this second process on a different
terminal session, the home terminal for the process itself remains unchanged, and
the process might attempt to prompt or output to its home terminal, causing more
contention. Because of this potential problem, use Visual Inspect as the preferred
debugger for multiprocess debugging.
2. Transfer the current process to the new Native Inspect instance:
a. From the new Native Inspect instance, enter the attach command.
b. From the original Native Inspect instance, release the current process (the
newer debugging target) by entering the detach command.
TACL> status *, term
Process Pri PFR %WT Userid Program file Hometerm
$Z160 3,301 123 R 000 8,12 $SYSTEM.SYS00.EINSPECT $ZP1.#PHF
TACL> einspect /cpu 3/










