;
DEBUG "Breakpoint" Command...
Breakpoint { <statement> | <routine-name> | -Exit | -Here |
-VA va_number | -VA <routine-name>\rva_number }
[-After <integer>] [-Trace] [-Do <action-list>]
A <routine-name> is:
<routine>\[<routine>\...]
A <statement> can be:
<line-no>[+<offset-no>]
<label>[+<offset-no>]
<routine-name><line-no>[+<offset-no>]
<routine-name><label>[+<offset-no>]
The -Exit option sets a breakpoint on the exit of the routine.
The -VA option sets a breakpoint on a virtual program address.
If "va_number" is given, this is taken to be some virtual address where
a breakpoint will go.
If "<routine-name>\rva_number" is given, then the routine is found, and
the "rva_number" is assumed to be a ZERO-RELATIVE number which is added
to the start of the named routine to make a virtual address breakpoint.
You can list -VA breakpoints ONLY by listing "all" breakpoints.
Remember that DEBUG assumes base 10; hexadecimal numbers must be given
with a leading "16#". Also, NO CHECK is done to see if the number
supplied is legal. We trust you!
The -Here option sets a breakpoint at the current program
location. (If a user environment is set, it is ignored.)
If you already have a breakpoint at the current program
location, it is replaced.
The -After option sets a counter for how many times the
statement can be executed before the break occurs. The
default is 1.
The -Trace option turns the breakpoint into a trace. When
the statement is executed, a message is given, the optional
<action-list> is done, and the program continues execution.
An <action-list> is a list of one or more commands,
separated by ";", and surrounded by square brackets [].