Breakpoints (Compact 2013)

3/26/2014

A breakpoint causes the debugger to pause execution at a certain point in a program. When a break occurs, the program enters a break state. A break state does not terminate or end the execution of the program. Functions, variables, and objects remain in memory, but their movements and activities are suspended. You can resume execution of the program at any time.

Breakpoint states

When you set a breakpoint, a breakpoint glyph appears in the margin to the left of the code. There are three different glyphs, each indicating a specific breakpoint state.

The following table describes the different breakpoint states and their associated glyphs:

State	Glyph	Description
Enabled, instantiated	Solid red circle	Indicates that a breakpoint is set and a .dll or .exe file, which was built by using the source file with the breakpoint, is loaded on the target device. The program breaks when it reaches this point in the execution.
Enabled, not instantiated	Hollow circle with a yellow caution triangle	Indicates that a breakpoint is set and the .dll or .exe file, which was built by using the source file with the breakpoint, is not loaded on the target device. At the next stopping event, the debugger will attempt to instantiate the breakpoint. If the breakpoint can be instantiated, the glyph color changes to red. If the breakpoint cannot be instantiated, verify that the module that you are trying to debug is loaded.
Disabled	Hollow circle	Indicates that a breakpoint is set, but it is disabled. The program does not break at this point. To make the breakpoint active, enable the breakpoint. For more information, see Enable Breakpoints.

To perform specific breakpoint tasks, see:

• Set Breakpoints
• Remove Breakpoints
• Enable Breakpoints
• Disable Breakpoints

See Also

Concepts

Kernel Debugger
Debugging

Other Resources

Windows Embedded Compact 2013