Inspect Manual

Low-Level Inspect
Inspect Manual—429164-006
7-5
Differences Between Low-Level Inspect and Debug
Differences Between Low-Level Inspect and Debug
The following subsections highlight the differences between low-level Inspect and
Debug.

Low-level Inspect does not support the DEBUG ALL parameter when setting
breakpoints.

Low-level Inspect allows B (break) and C (clear) to refer to breakpoints by block
name, representing the base of a program unit.

Low-level Inspect allows you to write the output of a display to a disk file or to a
nondisk file. Debug allows you to write only to a nondisk file.
Example of low-level Inspect commands:
D /OUT \sys.$vol.subvol.file/ 0,10 (Disk file)
D /OUT $s.#lp3/ 0,10 (Nondisk file)
Example of Debug commands:
D0,10,$s.#lp3 (Nondisk file)

Debug allows you to modify code locations. You cannot modify code locations with
either low-level or high-level Inspect.

The low-level Inspect commands D and M display extended addresses rather than
16-bit word addresses when the memory resides in an extended data segment.
For example, this D command displays memory from an extended data segment:
The A Command
The low-level A command without parameters provides an interpretation of the ENV
register and an indication of the current code segment.
The D Command
The D command in low-level Inspect differs from the D command in Debug. Here is the
syntax you use in Inspect.
_OBJECT_D 2000000, 4
00002000000: 000000 000000 000000 000000
D [ [ unit ] address [ , amount ] ] [ : base ]
[ register ]
unit: one of
B W D F