Native Inspect Manual (H06.03+)

Using Native Inspect
Native Inspect Manual—528122-003
2-2
Preparing to Debug Using Native Inspect
Preparing to Debug Using Native Inspect
Before you can use Native Inspect for debugging, you need to:
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. Configure a search path for source files.
5. Advance execution to main() (only for C/C++).
Compiling and Transferring Program Files
You can compile your program on either:
•
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). Remember that with optimization level 1:
•
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 are often live in registers, with write-through to memory.
•
The debugger displays only values that are known to be true.
Set a memory access breakpoint mab { addr | var }b data-loc
Delete a code breakpoint delete [ bkpt-num ] clear bkpt-num
Delete a memory breakpoint dmab clear number
Resume execution continue r
Machine State Commands
Display registers info registers or
info all-registers
or info frame num
d registers all
Display instructions disassemble [[addr]
[addr]| func ]
icode code-loc
Table 2-1. Principal Native Inspect Commands With Inspect
Equivalents (page 2 of 2)
Task
Native Inspect
Command Inspect Command
* Native Inspect displays source and looks up variables relative to the selected frame.