Native Inspect Manual (H06.04+)

Using Native Inspect
Native Inspect Manual—528122-005
2-3
Gaining Control of a Process Using Native Inspect
•
The debugger displays only values that are known to be true.
If you are developing your program on a remote system or on a Windows PC, transfer
your files to the system where you will perform debugging. You will need the program
files in addition to the DLLs you are using.
Gaining Control of a Process Using Native Inspect
To start a program under control of the debugger, use the TACL RUND command:
TACL 2> rund nitest
The debugger that is invoked by the RUND command is determined by a set of rules
described in Debugger Selection Criteria on page 1-9.
To debug a process that is running, use the TACL DEBUG command:
TACL 3> debug nitest , term $myterm
For complete information about other ways to gain control of a process using Native
Inspect, and for additional examples, see Starting Native Inspect on page 1-7.
Loading Symbols Information (If Necessary)
To debug a process using a symbolic debugger such as Native Inspect, symbols
information must be loaded for the process you want to debug. When Native Inspect
gains control of a process, it attempts to load symbols for the process.
You will need to explicitly load symbols if you want to debug:
•
A loadfile whose symbols have been stripped (typically done on production
systems to minimize file size). You must know the location of the identical version
that contains symbols.
•
Any DLLs that your program loads.
To load symbols, use the symbol command or symbol-file command
or the add-
symbol-file command:
symbol-file filename
For example, if you enter an unqualified file name, the file must exist in the current
working directory:
(eInspect 0,380): symbol-file xvod02a
xvod02a: No such file or directory.
(eInspect 0,380): symbol-file $d0101.qagarth.xvod02a
Reading symbols from $d0101.qagarth.xvod02a...done.
You must enter separate symbol commands for all files of interest — one symbol
command to load the symbols for your program file, and separate symbol commands
for each DLL.