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

Using Tcl Scripting
Native Inspect Manual—528122-003
4-3
Using Variables Defined in a Tcl Script
Using Variables Defined in a Tcl Script
You can use variables defined in a Tcl script, such as $amount, after you run the Tcl
script that contains the definition.
The Tcl interpreter treats all command arguments as Tcl scripts. The Tcl environment
is persistent for each interactive session, so variables you create and values you set
are retained. For example:
(eInspect 3,301): tcl set x 0xabcd
(eInspect 3,301): tcl puts $x
0xabcd
Programming Native Inspect Tcl Commands
The Tcl Style Guide (http://www.tcl.tk/doc/styleGuide.pdf) provides a structure for Tcl
script headers and the layout of package namespaces. The structure consists of:
•
File header
°
Abstract
°
Copyright notice
°
Revision string
°
Package definition (package name, namespace, version)
•
Procedure headers (one or more)
°
Abstract
°
Arguments
°
Results
Namespaces and Package Loading Rules
Tcl supports packages and hierarchical namespaces.
Creating Packages
Packages are libraries of Tcl code that you can create using the Tcl package provide
command:
# mySub.tcl
package provide mySub 1.0
# my package code
Putting a Package in a Namespace
The global namespace contains the built-in Tcl commands, such as set, puts, and
open. You should create your Tcl packages in your own child namespace, not in the
global namespace, which should be the exclusive property of the application.










