From d10d441087dc1a7edd44eebe40c78db7b652a7fc Mon Sep 17 00:00:00 2001 From: Jose Antonio Ortega Ruiz Date: Sat, 21 Jul 2001 22:09:03 +0000 Subject: conditional breakpoints --- doc/mdk_gstart.texi | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'doc/mdk_gstart.texi') diff --git a/doc/mdk_gstart.texi b/doc/mdk_gstart.texi index 4c8b025..25764a0 100644 --- a/doc/mdk_gstart.texi +++ b/doc/mdk_gstart.texi @@ -423,7 +423,11 @@ thus, in the above example we have requested a breakpoint at a line which does not correspond to a MIX instruction and the breakpoint is set at the first line containing a real instruction after the given one. To unset breakpoints, use @code{cbpa ADDRESS} and @code{cbp LINE_NO}, or -@code{cabp} to remove all currently set breakpoints. +@code{cabp} to remove all currently set breakpoints. You can also set +conditional breakpoints, i.e., tell @code{mixvm} to interrupt program +execution whenever a register, a memory cell, the comparison flag or the +overflow toggle change using the commands @w{@code{sbp[rmco]}} +(@pxref{Debug commands}). MIXAL lets you define symbolic constants, either using the @code{EQU} pseudoinstruction or starting an instruction line with a label (which -- cgit v1.2.3