RubyMine 4.0.0 Web Help

Run | View Breakpoints

Ctrl+Shift+F8Command Shift F8

debug_view_breakpoints

Run | View Breakpoints

Ctrl+Shift+F8Command Shift F8

debug_view_breakpoints

Use this dialog to:

Warning

If you haven't set any breakpoints in your code, behavior options are hidden. To configure them, you should first create a breakpoint. Options are displayed for the currently selected breakpoint only.

The dialog box consists of tabs corresponding to the types of breakpoints and the contexts in which breakpoints are set. The controls for all types of breakpoints are similar; differences are specially noted.

Each tab contains the following groups of controls:

Buttons

Item Breakpoint type Description
Add Exception breakpoints Click this button to create a new exception breakpoint to handle exceptions that belong to a certain class. Note that if you have several exceptions belonging to the same hierarchy, the most specific exceptions will be handled on the corresponding exception event, and the more general ones will be ignored.
Go to Line breakpoints Navigates to the selected breakpoint, positions the caret at the corresponding line and closes the dialog box.
View Source Line breakpoints Pressing this button results in navigating to the code page with the selected breakpoint, positioning the caret in the appropriate line, but the dialog box remains open.
Remove All Removes selected breakpoints. If all breakpoints are removed from the list, the lower pane would have no selection groups available and all buttons except for Close would be disabled.

Suspend policy

Item Description
Suspend When a breakpoint is hit in a thread, only that thread is suspended.

Actions

Item Breakpoint type Description
Log message to console All types Select this check box if you want a log message to be displayed in the console output when the breakpoint is hit.
Log evaluated expression Line breakpoint Select this check box if you wish to evaluate a certain expression at this breakpoint and to export result to the console output.

Tip

If the expression to be evaluated is incorrect when a particular breakpoint is reached, the console output displays an error message: Unable to evaluate the expression <your_expression>.

Depends on

Item Description
Depends on Here you can set a breakpoint the current one will depend on. Thus the dependent, slave breakpoint is conditionally disabled - it becomes enabled only if the master breakpoint is hit. Hence you can form cascades of dependent breakpoints to satisfy any requirements.
After breakpoints was hit Select the behavior of the slave breakpoint after hitting the master breakpoint: disable it again or leave it enabled.

Conditions

Item Breakpoint type Description
Condition Line breakpoints Select this check box and specify a condition for hitting a breakpoint in the text field.

A condition is a Boolean expression, which should be valid at the line where the breakpoint is set, and is evaluated every time the breakpoint is reached. If the evaluation result is true, user-selected actions are performed. If the result is false, the breakpoint does not produce any effect. If the Debugger cannot evaluate the expression, it displays the Condition evaluation error message. You can select whether you would like to stop at this breakpoint or ignore it.

See Also

Concepts:

Procedures:

Web Resources: