User`s guide

64
Chapter 6: Controlling Program Execution
The following forms of the stop command combine both the variable and test
clauses:
stop [expression1|variable] if expression2
Tests both conditions before executing each source line.
Stops if both conditions are true.
If expression1 is of type pointer, look at the data pointed to
and watch until it changes. If expression1 is not of type
pointer, look at the 32 bits at that address (assume the
expression evaluates to an address).
stop [expression1|variable] at line if expression2
Tests both conditions at the given source line. Stops if both
conditions are true.
If expression1 is of type pointer, look at the data pointed to
and watch until it changes. If expression1 is not of type
pointer, look at the 32 bits at that address (assume the
expression evaluates to an address).
stop [expression1|variable] in procedure if expression2
Tests both conditions at every source line within a given
procedure. Stops if both conditions are true.
If expression1 is of type pointer, look at the data pointed to
and watch until it changes. If expression1 is not of type
pointer, look at the 32 bits at that address (assume the
expression evaluates to an address).
Continuing Execution After a Breakpoint
The cont command allows you to continue execution after any type of
breakpoint. In its simplest form, program execution continues until the end
of the program or until another breakpoint is reached. You can also tell dbx
to continue your program until it reaches a given line or procedure; this is
similar to setting a temporary, “one-shot” breakpoint and then continuing.
The syntax of the cont command is:
cont Continues execution with the current line.