Inspect Manual

Using Inspect With Pascal
Inspect Manual—429164-006
12-15
Inspect Enhancements and Restrictions for Pascal
Inspect Enhancements and Restrictions for
Pascal
The following subsection discusses the difference between programming with Pascal
and using Inspect to debug Pascal programs.
Length of Identifiers
Note that a Pascal identifier can be any length, but Inspect only accepts the first 31
characters.
Command Usage Guidelines for Pascal
Programmers
The following guidelines for Pascal programmers using Inspect are arranged
alphabetically by Inspect command name. Not all commands are listed.
BREAK

You can set a code breakpoint at a line number, procedure name, or label name. If
the number or name is not in the current scope, you must qualify it with a scope
name.
You can also set a code breakpoint at an offset from a line number or label, or at
an offset from a primary entry point. Specify offsets as a number of statements or
instructions.

If you set a breakpoint at the entry point of a scope unit, the break event it triggers
will occur before any initialization. Consequently, you should enter a STEP 1 S
command after the break event.

Because a data breakpoint is associated with a single word, an identifier
designating multiple words (such as LONGINT) has only its first word marked as
the breakpoint.
HELP
You can ask for help on the definitions of Inspect command parameters. Therefore,
you can find out what Inspect recognizes as a Pascal data location, a Pascal code
location, a Pascal expression, or a Pascal conditional expression.
INFO IDENTIFIER

Like Pascal, Inspect requires complete name qualification of record elements. If
you request a listing of the attributes of an unqualified data name, and the only
instance of that name is in a record, Inspect will give you an error message. If the
data name occurs in the scope twice—once as a simple variable and once as part