Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Breakpoint Properties
Breakpoints in Enterprise Architect support a number of additional properties that change when a breakpoint is hit, and determine what happens when it is hit.
Access Breakpoint Context Menu | Properties
Use to
| • | Change breakpoint actions |
| • | Move the breakpoint to another line |
| • | Add constraints to restrict when a breakpoint is hit |
| • | Add information to be logged when the breakpoint is hit |
Reference
Field |
Usage |
See also |
|---|---|---|
Action |
Change the behavior when the breakpoint is hit.
|
|
Line |
Change the line that this breakpoint is on.
|
|
Constraints |
Associate a condition with the breakpoint. The program is allowed to run if the condition is not met when the breakpoint is encountered.
|
|
Log |
Log information to the Debug window when the breakpoint is hit.
|
Specifying constraints:
You can compose constraints using any variables that are in scope at the time the breakpoint occurs.
m_strName="John"
m_strName=""
m_nCount > 0
You can also join constraints using logical operands, for example:
m_strName="John" AND m_nCount > 0
You can access elements of an array or pointer, for example:
m_pNames[10]="John"
You can also nest constraints using parentheses to impose precedence, for example:
( x>0 AND y>0) OR (x < 0 AND y < 0)
Adding log information:
Add your trace statement into the Log field. To output a string variable, prefix the variable name with the '$' token and for primitive types use an '@' token .
Example for outputting a string member named m_Name of an object named X.
The value of m_Name = $X.m_Name
Example for outputting an integer named m_Count of an object named X.
The value of m_Count = @X.m_Count
Learning Center topics
| • | (Alt+F1) | Build and Debug | Debug | Breakpoint Properties |
