Migrating from Inspect to Native Inspect

Migrating from Inspect to Native Inspect
Hewlett-Packard Company 543427-002 3 of 15
list line-number
list file:line-number
Inspect Difference: Native Inspect does not
support the ability to search for text in source
files or to close open source files.
Gotcha: In Native Inspect, the source
command has the same meaning as the Inspect
OBEY command.
If Native Inspect cannot locate your source
files, see Locating Source and Symbols on
page 6.
To obtain information about source files,
use these Native Inspect commands:
info source List information about
current source file.
info sources List information about all
accessed source files.
Tracing the Stack
In Native Inspect, use the bt (back trace)
command to list the frames on the call stack.
When debugging, you often gain control of a
process in a low-level function and then
need to determine the circumstances that
lead to it being called. To select the
specified frame as the frame relative to
which the debugger displays program state,
use the command:
frame frame-number
This command serves the same function as
the Inspect SCOPE frame-number command.
Native Inspect also has up and down
commands for selecting the preceding or
succeeding stack frame.
Tip: If you forget the location at which your
program is suspended, issue the frame 0
command, abbreviated fr 0, to display the
current execution location.
By default Native Inspect lists function
arguments in the stack trace. The following
command disables this behavior:
set print args off
To obtain detailed information about a stack
frame, use the info frame command.
Controlling Program
Execution
Native Inspect supports the same concepts
as Inspect for stepping program execution
but uses different command names to refer
to the operations:
Inspect Native Inspect
STEP [OVER]
next or n
STEP IN
step or s
STEP OUT
finish
Process-control commands are also
different:
Inspect Native Inspect
RESUME
continue or c
STOP
kill or k
Breakpoints
Native Inspect supports the same breakpoint
concepts as Inspect, though they are written
differently.
To set a breakpoint, use one of these forms
of the break command, abbreviated b:
break line-number
Set breakpoint on a
line number.
break file:line
Set a breakpoint on a
line number in the
specified file.
break function
Set a breakpoint at the
entry to a function.
break label
Set a breakpoint at a
code label.
break paragraph
Set a breakpoint on a
COBOL paragraph.
break paragraph OF section
Set a breakpoint on a
COBOL paragraph in
the specified section.
Inspect Difference: Unlike Inspect, code
location specifications are not prefixed with a #.
If there are multiple instances of a specified
function, Native Inspect displays a selection
menu.
To set a temporary breakpoint, use the
tbreak command.