Inspect Manual

Inspect Concepts
Inspect Manual—429164-006
2-10
Setting Breakpoints
Inspect puts the program into the hold state, reports the breakpoint, and then performs
any break action associated with the breakpoint.
Setting Breakpoints
Inspect maintains a breakpoint list for each program you are debugging, and enables
you to add breakpoints to or to remove breakpoints from the current program's
breakpoint list. The time at which you set a breakpoint is called breakpoint definition.
Code Breakpoints
A breakpoint whose break location refers to object code (whether at the source or
machine level) is called a code breakpoint. In Inspect, you specify the location of a
code breakpoint using a code location. Code breakpoints are activated when the code
specified by the code location is about to be executed.
When debugging on a TNS/R system, code breakpoints may be set at any location in
non-accelerated or TNS/R native programs. However, when debugging accelerated
programs, Inspect only allows TNS code breakpoints to be set at location that are
memory-exact points. An attempt to set a TNS breakpoint at a location that is not a
memory-exact will result in an error. Fore more information, see Section 16, Using
Inspect With Accelerated Programs on TNS/R Systems.
When debugging PATHWAY requester programs, you can put code breakpoints in
inactive scope units only at the entry point of the scope unit.
Data Breakpoints
A breakpoint whose break location refers to a data item is called a data breakpoint. In
Inspect, you specify the location of a data breakpoint using a data location. Data
breakpoints are activated when the data word specified by the data location is stored to
or (optionally) read from or changed. This detection of read access extends to the
special, read-only data types provided by some languages (for example, P-relative
arrays in TAL).
The default type for high-level data breakpoints is change (formerly write). The new
default applies to both TNS and TNS/R systems. Data breakpoints are only reported if
the value of the variable has changed; writes that store the same value already
Note. Inspect does not limit the number of breakpoints you can set in a single program.
However, after breakpoint ninety-nine, Inspect will stop numbering them. The total number of
code breakpoints in all processes and PATHWAY servers running in a single processor is
further limited; it is specified by BREAKPOINT_CONTROL_BLOCKS at system generation
time. Consult your system operator or system manager for the maximums used in your
system's processors.
The total number of code breakpoints in all PATHWAY requester programs under the control of
a single TCP cannot exceed twenty.