Table of Contents
Advertisement
Debugging
177
Executing an IBREAK statement from the keyboard is effective only for the environment
executing at the time the statement is made. For example, if the following program lines had
been executed -
and while the pause caused by line 210 is still in effect-
is executed, then the break point established for "Hook" is good only in the subprogram
"Test". As with the above, leaving Test causes the break point to be cleared.
If no program is executing when an IBREAK is executed from the keyboard, then the main
program is considered to be the environment for the break point. If the program is replaced, as
with a GET or a LOAD, then the break point is cleared.
Data Locations
Break points can also be established for data locations. This is done with -
In this case, {address} is presumed to be a data location referenced by other instructions.
Whenever it is referenced by execution of some instruction, the pause occurs.
If
you were to say -
'r
•. !..
then whenever "Renras" is referenced, such as in -
a pause would occur for that instruction.
Advertisement
Table of Contents
