Native Inspect Manual (H06.13+, J06.03+)

1. Compile your program files, and transfer them to the TNS/E host if necessary.
2. Gain debugging control of a process by using Native Inspect.
3. Load symbols information for the current process, if necessary.
4. Optionally, configure a search path for source files.
These steps are described in more detail in the following sections.
Compiling and Transferring Program Files
You have the following options for compilation:
• The TNS/E host by using a resident compiler.
• A PC by using the Windows cross-compiler for HP NonStop systems.
Compile your code with optimization level 0 or 1 (code compiled with optimization level 2 cannot
readily be debugged). With optimization level 1, the following conditions apply:
• Statements might be deleted or merged.
• The debugger can display live data, but data no longer needed by the program might not be
available.
• Values often reside in registers, with write-through to memory.
• The debugger displays only values that are known to be true.
If you are developing your program on a remote TNS/E 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
the section titled: Debugger Selection Criteria (page 20).
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 (page 19).
Optionally Loading Symbols Information
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 the following:
• 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, symbol-file command, or 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.
34 Using Native Inspect