Breakpoint Properties

Breakpoints have a number of additional properties that change the point at which the breakpoint is hit, and that determine what happens at that point. These properties define:

Any changes in action or behavior
The line of code that the breakpoint moves to
New constraints to restrict when the breakpoint is hit
Information to be logged when the breakpoint is hit

Access     Breakpoint Context Menu | Properties




See also


Identifies the change in behavior when the breakpoint is hit.


Marker Types


Changes the line that this breakpoint is on.




Associates a condition with the breakpoint.

The program is allowed to continue if the condition is not met when the breakpoint is encountered.

You can:

Compose constraints using any variables that are in scope at the time the breakpoint occurs; for example:
m_nCount > 0


Join constraints using logical operands, for example:
(m_strName="John") AND (m_nCount > 0)


Access elements of an array or pointer, for example:


Nest constraints, using parentheses; the debugger requires explicit precedence, for example:
((x > 0) AND (y > 0)) OR ((x < 0) AND (y < 0)) OR ((x = 0) AND (y = 0))



Trace statement

Logs information to the Debug window when the breakpoint is hit.

To output a string variable, prefix the variable name with the '$' token; for primitive types use an '@' token.


Example of outputting a string member named m_Name of an object named X.

                The value of m_Name = $X.m_Name


Example of outputting an integer named m_Count of an object named X.

                The value of m_Count = @X.m_Count


Run the Debugger

Learning Center topics

(Alt+F1) | Build and Debug | Debug | Breakpoint Properties