JetBrains Rider 2017.2 Help

Breakpoints

Run | View Breakpoints
Ctrl+Alt+B

Toolbar

ItemTooltip and shortcutDescription
add rider icon Add Breakpoint
Alt+Insert
Click to show the list of available breakpoint types. Select the desired type to create a new breakpoint.
remove rider icon Remove BreakpointClick this button to remove selected breakpoints.

Breakpoint options

The controls of this part of the Breakpoints dialog depend on the type of the selected breakpoint.

OptionDescription
Enable Select this check box to enable a breakpoint. If the breakpoint is disabled, it won't be hit during debugging.
SuspendSelect this check box if you want the debugger to suspend the program when the breakpoint is hit. It makes sense to disable this option, for example, if you want the breakpoint only to log some data or calculate an expression at some point without suspending the program.
Condition Select this check box and specify a condition for hitting a breakpoint in the text field.
Log message to console Select this check box if you want a log message to be displayed in the console output when the breakpoint is hit.
Evaluate and logSelect this check box if you wish to evaluate a certain expression at this breakpoint and to export result to the console output.

To the right of this field, there is the button shift enter button(Shift+Enter) that opens the multiline editor.

Remove once hitSelect this check box, if the you want the breakpoint to be deleted after hitting it.
Disabled until selected breakpoint is hitFrom the drop-down list, select the breakpoint you want the current breakpoint to depend on. The option None corresponds to the always enabled breakpoint.

Besides that, you can also choose the behavior of this breakpoint, when the selected one is hit:

  • Disable again
  • Leave enabled
Hit count Specify the integer number, on which hit of the breakpoint it should be triggered. After the specified number of passes, the breakpoint is hit.

This function is helpful for debugging loops or methods called several times. When the execution process comes to a breakpoint, where Hit count is set, the debugger reduces the count value by 1 and compares it to zero. If the comparison result is true, the breakpoint is hit. If it is false, no other actions are performed until the next breakpoint is reached.

The Hit count condition can be satisfied only once. In other words, if you have a loop inside a method and the Hit count condition has been honored once, the breakpoint will not be hit the next time the said method is called.

Context menu commands

CommandDescription
Move to groupPoint to this command to move the selected breakpoint to a new group, to one of the existing groups(<group name>), or out of a group (style="inline"><no group>).
Edit descriptionChoose this command to enter or change description of a breakpoint.
Last modified: 17 November 2017