Inspect Manual

High-Level Inspect Commands
Inspect Manual—429164-006
6-161
Usage Considerations
Usage Considerations

All save files created by Inspect are of type unstructured and have a file code
ofþ130.

Inspect qualifies filename using the current subvolume if systype is Guardian or the
current working directory if systype is OSS. If you have not set the volume and
subvolume explicitly, they are the default volume and subvolume of the Inspect
session. Use the ENV command to determine these defaults.

If the only program you are debugging is a save file, entering the STOP command
closes the save file but does not end the Inspect session, as it does for processes.
In this case, you must enter the EXIT command or press CTRL/Y.

To begin analyzing a save file, enter an ADD PROGRAM command with the save
file name. You can use any high-level or low-level command that does not change
the execution state of the process; therefore, you can display code values, data
values, attributes, and a stack trace. Many commands that are available when a
process is in the hold state, however, are unavailable when you are working with a
save file. These commands include:
BREAK
CLEAR
FB
HOLD
LIST BREAKPOINT
MODIFY
RESUME
SELECT DEBUGGER DEBUG
STEP
Related Commands

ADD PROGRAM on page 6-10

INFO SAVEFILE on page 6-120

STOP on page 6-215