Inspect Manual

Inspect Manual—429164-006
3-1
3 Inspect Command Overview

Debugging the Current Program

Managing Multiple Programs on page 3-3

Managing Source Files on page 3-3

Entering and Editing Inspect Commands on page 3-4

Customizing an Inspect Session on page 3-5

Managing an Inspect Session on page 3-6
For detailed descriptions of the high-level and low-level Inspect commands, see
Section 6, High-Level Inspect Commands, and Section 7, Low-Level Inspect.
Entering Inspect Commands
Inspect processes commands on a line-by-line basis. When it reads a line, whether
from the Inspect command terminal, the INSPLOCL file, the INSPCSTM file, or an
OBEY file, Inspect expects that line to be either:

A blank line

A command list
A command list consists of either a single Inspect command or a list of Inspect
commands separated by semicolons. If a command list includes an alias name,
Inspect substitutes the alias's replacement text for its name.
If a command list is too long to fit on a single line, you can continue it on the next line
by ending the first line with an ampersand (&). For example, assume you enter this:
The effect is that same as this:
Using the ampersand to continue the command list, you can create command lists of
up to 512 characters, including the space required to expand any aliases in the
command list.
There are two cases for pressing the BREAK key:

When entering an Inspect command
Pressing BREAK returns you to the TACL prompt. Enter PAUSE to return to
Inspect.

When fixing a command (within the FC command)
-PRG-DISPLAY height, width, &
-PRG-depth, (height*width*depth)
-PRG-DISPLAY height, width, depth, (height*width*depth)