Inspect Manual

High-Level Inspect Commands
Inspect Manual—429164-006
6-163
Usage Considerations
Usage Considerations

To examine an element as it exists during a particular instance, include an instance
number when you specify the scope path. You can count from either direction
using these conventions:

Instance 1 is the least recent instance—that is, the oldest chronologically.
Positive values count from the base of the stack toward the top.

Instance 0 is the most recent instance—that is, the current scope path.

Instance -1 is the next most recent—that is, the youngest chronologically.
Negative values count from the top of the stack toward the base.

There is a subtle difference between an unspecified instance and instanceþ0.
Suppose you have a scope unit named BINK. You can set your scope path to
#BINK whether BINK is active or not; you can set your scope path to #BINK(0)
only if BINK is active. If you set your scope path to #BINK and the scope unit is
active, then #BINK(0) and #BINK are identical.

If the current program is not in the hold state when you enter a SCOPE command
without parameters, Inspect displays the scope path that was active at the time the
command was received.

If you set your scope path to a data block, you cannot set unqualified code
breakpoints.

Whenever a debug event occurs, Inspect sets the current scope path to the path
that specifies the scope unit containing the location at which the event occurred.
Related Commands

ENV on page 6-81

INFO SCOPE on page 6-122

MATCH with the SCOPE option on page 6-144

TRACE on page 6-219