Breakpoints

A good way to debug problems is by adding breakpoints to the code. The POOSL IDE supports line breakpoints in process methods (Debugging of data methods is not yet supported). A breakpoint cannot be added on a statement of these types:

Abort statement (abort .. with)
Interrupt statement (interrupt .. with)
Parallel statement (par .. and .. rap)
Select statement (sel .. or .. les)

A breakpoint can however be set to the constituents of these statements.

Adding/Removing breakpoints

Adding a breakpoint can be done in 3 different ways:

Double click the ruler in front of the line in the editor.
Right click the ruler in front of the line and select Toggle Breakpoint.
Use the shortcut Ctrl+Shift+B to set/remove a breakpoint on the current line.

If a breakpoint is set, a blue dot appears in front of the line. When there are multiple statements on one line, the breakpoint will always be set to the first statement on that line.

Enable/Disable breakpoints

Breakpoints will be listed in the Breakpoints view that is visible in the bottom of the Edit/Debug perspectives. (If the Breakpoints view is not visible, then reset the perspective by right clicking the perspective in the upper right hand corner and selecting Reset).

The checkbox in front of a breakpoint can be used to enable or disable a breakpoint so that the breakpoint remains set but can be deactivated or activated when needed. To Enable or disable all breakpoints at the same time use button in the top of the view.

Breakpoint hits

When a breakpoint is hit during simulation, the simulation will suspend. The breakpoint that was hit will be highlighted in the Execution Tree view and highlighted in the editor.