Inspect Manual

Inspect Concepts
Inspect Manual—429164-006
2-11
Processing Breakpoints
contained in the variable are not reported. You can have only one data breakpoint at a
time in each program that you are debugging.
Conditional and Unconditional Breakpoints
A breakpoint whose definition includes a break condition is called a conditional
breakpoint. If a breakpoint's definition does not include a break condition, it is called
an unconditional breakpoint. The conditionality of a breakpoint affects how Inspect
processes the breakpoint, as discussed in the following subsection.
Processing Breakpoints
Whenever one of the programs you are debugging encounters a break location,
Inspect begins processing the breakpoint at that break location. This is called
breakpoint activation. If the breakpoint is unconditional, Inspect generates a break
event immediately. On the other hand, if the breakpoint is conditional, Inspect does not
generate a break event unless the specified break condition is met. Once the break
event occurs, Inspect suspends the program containing the breakpoint.
After recording the current breakpoint, Inspect performs any break action associated
with the breakpoint. If the break action concludes with a RESUME command, Inspect
does not display the status messages and prompt as it normally would; instead, it
resumes execution immediately.
Source Languages and Inspect
To support several source languages, Inspect uses generic concepts to describe a
program and its contents. These concepts include:

Scope of identifiers

Scope units and scope paths

Activation of scope units, including recreative activation

Expressions

Code locations

Data locations
The availability and applicability of these concepts differ from language to language;
however, Inspect presents them similarly whenever possible.
Note. Specific constraints apply to data breakpoints when executing accelerated programs on
TNS/R systems. For more information, see Section 16, Using Inspect With Accelerated
Programs on TNS/R Systems. In addition, data breakpoints are not valid in PATHWAY
requester programs