Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- Watcom Debugger Guide - when debugging, you will often want to set a few simple breakpoints to make http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
When debugging, you will often want to set a few simple breakpoints to make
your program pause execution when it executes certain code.  You can set or
clear a breakpoint at any location in your program by placing the cursor on
the source code line and selecting Toggle from the Break menu or by clicking
on the button to the left of the source line.  You can set breakpoints in
the assembly window in a similar fashion.  Setting a break-on-write
breakpoint is equally simple.  Select the variable with the right mouse
button and choose Break from the pop-up menu.

Break points have three states.  They are:

 .  enabled
 .  disabled
 .  cleared (non-existent)

The button for an enabled break point is a stop sign or [!].  The button for
a disabled break point is a grey stop sign or [.].  A green diamond or [ ]
appears when no breakpoint exists at the given line.  The same buttons also
appear in the Assembly window and the Break window to indicate the status of
a break point.

Note:
    Some lines in your program do not contain any machine code to execute
    and therefore, you cannot set a breakpoint on them.  The compiler does
    not generate machine code for comments and some C constructs.  All lines
    of code in your program that can have a breakpoint on them have a button
    to the left of the source line.  You can click on them to change their
    current status.

Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson