Breakpoint Overview (Windows Embedded CE 6.0)

1/5/2010

When execution is in a break state, functions, variables, and objects remain in memory, but their movements and activities are suspended.

Breakpoint types

Windows Embedded CE provides three types of breakpoints:

Location breakpoints, which cause execution to stop when the code reaches a certain location.
Message breakpoints, which cause execution to stop when a particular function message is reached.
Data breakpoints, which cause execution to stop when the value of data at a certain location changes, or when a referenced Boolean expression is true.
Data breakpoints have the following restrictions:
- They must be set on global variables.
- They must be enabled while in the module or context, or while the .exe file is running.
- They must be disabled when outside the module or context, or when the module is no longer running.
- They must be set in a source file that has no spaces in its path.
- They can only be instantiated on a new instance of an existing module if the existing breakpoint was instantiated on one module at a time.
- If the existing breakpoint was instantiated on multiple modules, either simultaneously or after a secondary module loaded, the breakpoint cannot be split.
- When a new module loads and a line contains multiple breakpoints that are not all of the same state, the breakpoints are displayed in an undefined state.