Table of Contents
Advertisement
Debugging
179
This statement overrides all other IBREAK statements and causes a pause before execution of
every instruction in the ICOM region. There are also branching forms -
I:EF'f:-=r::jf·<
' - . J !
C:HL.J. __ . {subprogram}
I
BF~EJ::!i-<
! .•••• !!
C;C<:;UB {line identifier}
I
BF~!E~F+::'
C! {line identifier}
Note, however, that there is no {counter} in any of these forms.
Number of Break Points
As was mentioned above, there can be no more than eight (8) IBREAK statements in effect at
one time, that is to say within the same environment. And only one IBREAK ALL can be in
effect at a given time.
In addition, there can only be one IBREAK or IBREAK DATA each in effect for a given
{address}. Executing an IBREAK or IBREAK DATA with the same {address} as specified in an
already effective IBREAK or IBREAK DATA statement causes the newly-executed statement to
override the previous one. While there may be an IBREAK and IBREAK DATA both for the
same {address}, the capability is not a useful one.
Clearing Break Points
There are a number of ways that break points can be cleared. One way as has already been
mentioned, is leaving the BASIC environment, which clears any GOSUB or GOTO type of
break points. Another way is to reassemble the module containing the break points. A third way
is to execute an INORMAL statement. This statement has the form -
After execution of the statement, whatever form of break point is established for the address
(except IBREAK ALL) is cleared.
If {address} is omitted in this statement -
then all break points are cleared. This is the only way to clear an IBREAK ALL which may be in
effect.
Advertisement
Table of Contents
