Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Breakpoint Properties
Breakpoints have a number of additional properties that change the point at which the breakpoint is hit, and determine what happens at that point. These properties define:
- The action to be performed
- The line of code that the breakpoint applies to
- Constraints to restrict when the breakpoint is hit
- Trace information to be output when the breakpoint is hit
Access Breakpoint Context Menu | Properties
Ctrl+Click breakpoint marker
Options
Field |
Details |
See also |
---|---|---|
Action |
The behavior when the breakpoint is hit. |
Marker Types |
Line |
The line of source code that this breakpoint applies to. |
|
Stack Height |
For Stack Capture markers, the number of caller frames to record. To record the entire Stack, set the value to 0. |
|
Constraints |
Defines the condition under which the breakpoint action will be taken. For normal breakpoints this would be the condition that halts execution. In this example, for a normal breakpoint, execution would stop at this line when the condition evaluates to True. Constraints are evaluated each time the line of code is executed. (this.m_FirstName=='Joe') AND (this.m_LastName='Smith') |
Constraint Composition |
Trace statement |
A message output to the Debug window when the breakpoint is hit. Variables currently in scope can be included in a trace statement output by prefixing the variable name with a $ token for string variables, or an @ token for primitive types such as int or long. For example: Account $pAccount->m_sName has a balance of @pAccount->m_fBalance |
Specifying a Trace Statement Run the Debugger |
Learning Center topics
- Alt+F1 | Enterprise Architect | Build and Debug | Debug | Breakpoint Properties