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
Syntax of Native Inspect Commands
Native Inspect Manual—528122-003
3-14
break command, tbreak command
Setting Global Breakpoints
Global breakpoints are breakpoints that are set using the -g command option. To
set global breakpoints, you must be logged on as the super ID, you must turn on
priv mode by using the priv command, and no one else can be performing global
debugging at the same time. A global breakpoint is triggered by any process that
executes the code on which the global breakpoint is set.
Examples
To set code breakpoints:
To list breakpoints:
To define a breakpoint condition:
Note. Set global breakpoints when debugging a problem in code that is shared by multiple
processes. However, use global breakpoints with care because they might result in numerous
processes being suspended in the debugger.
(eInspect 1,325):b 216
Breakpoint 1 at 0x70001670:2: file \SIERRA.$YOSE1.SYMBAT1.SCXXTST, line
216.
(eInspect 1,325):b test_complexTypes
Breakpoint 2 at 0x70003700:0: file \SIERRA.$YOSE1.SYMBAT1.SCXXTST, line
420.
(eInspect 1,325):
(eInspect 1,325):info break
Num Type Disp Enb Address What
1 breakpoint keep y 0x70001672 in main
at
\SIERRA.$YOSE1.SYMBAT1.SCXXTST:216
2 breakpoint keep y 0x70003700 in test_complexTypes
at
\SIERRA.$YOSE1.SYMBAT1.SCXXTST:420
(eInspect 1,329):b 352
Breakpoint 1 at 0x70002540:0: file \SIERRA.$YOSE1.SYMBAT1.SCXXTST, line
352.
(eInspect 1,329):condition 1 pcb->pin == 2
(eInspect 1,329):info break
Num Type Disp Enb Address What
1 breakpoint keep y 0x70002540 in pcbDataStructs_initialize
at
\SIERRA.$YOSE1.SYMBAT1.SCXXTST:352
stop only if pcb->pin == 2