| Prev | Next |
Breakpoint and Marker Management
Breakpoints work in Enterprise Architect in the same way as in any other Debugger. Markers are similar to breakpoints, but in Enterprise Architect they have special powers. Simply put, markers perform actions - such as recording execution and analysis - that breakpoints do not. The action of a breakpoint is always to stop the program.
You set any marker or breakpoint in the Source Code editor, where they are visible in the left margin. Clicking in this margin will add a breakpoint at that line. Breakpoints and markers are interchangeable - you can change a breakpoint into a marker and vice versa, using its 'Properties' dialog. You can quickly view and edit a breakpoint or marker's properties using either on its icon in the editor margin or in the Breakpoints and Markers window.
Breakpoints are maintained in sets. There is a default set for each model and each breakpoint typically resides there, but you can save the current breakpoint configuration as a named set, create a new set and switch between them. Breakpoint sets are shared; that is, they are available to the model community. The exception is the Default set which is a private and personal set allocated to each user of any model.
Access
|
Ribbon |
Execute > Windows > Breakpoints Simulate > Dynamic Simulation > Breakpoints |
Breakpoint and Marker Options
Option |
Detail |
See also |
|---|---|---|
|
Delete a breakpoint or marker |
To delete a specific breakpoint:
|
Setting Code Breakpoints |
|
Delete all breakpoints |
Click on the ( |
|
|
Breakpoint properties |
In the Breakpoints window or code editor, use the marker's context menu to bring up the properties. Here you can change the marker type, add or modify constraints and enter trace statements. (Useful shortcut: hold the while clicking the marker, to quickly show its properties.) |
Recording |
|
Disable a breakpoint |
Deselect the checkbox against the breakpoint or marker. |
|
|
Enable a breakpoint or marker |
Select the checkbox against the breakpoint or marker. |
|
|
Disable all breakpoints |
Click on the |
|
|
Enable all breakpoints |
Click on the Enable all breakpoints button ( |
|
|
Break when memory address is modified |
Click on the Data breakpoint button ( |
|
|
Identify or change the marker set |
Check the If necessary, click on the drop down arrow and select a different marker set. The Default set is normally used for debugging and is personal to your user ID; other marker sets are shared between all users within the model. |
Working with Marker Sets |
|
Change how breakpoints and markers are grouped on the Breakpoints & Events window |
The breakpoints and markers can be grouped by Class or by code file. To group the items, click on the down arrow on the |
).
button
).
). 
field in the 
icon in the toolbar, and click on the appropriate option. If you do not want to group the items, click on the selected option to deselect it; the breakpoints and markers are then listed by line number.Breakpoint States
State |
Remarks |
See also |
|---|---|---|
|
Debug Running: Bound Debug Not Running: Enabled |
|
|
Debug Running: Disabled Debug Not Running: Disabled |
|
|
Debug Running: Not bound - this usually means that a module is yet to be loaded. Also, dlls are unloaded from time to time. Debug Not Running: N/a |
|
|
Debug Running: Failed - this means the debugger was unable to a match this line of code to an instruction in any of the loaded modules. Perhaps the source is from another project or the project configuration is out of date. Note, that if the module date is earlier than the breakpoint's source code date you will see a notification in the debugger window. The text is red in color so they will stand out. This is clear sign that the project requires building. Debug Not Running: N/a |
Failure to Bind Breakpoint |