JetBrains Rider 2018.2 Help

Debug window

View | Tool Windows | Debug
Alt+5

This tool window becomes available when you start debugging.

It displays the output generated by the debugging session for your application. If you are debugging multiple applications, the output for each application is displayed in a separate tab named after the corresponding run/debug configuration.

For each application, there are the following nested tabs:

  • Console: displays system information and error messages, and the console input and output of your application.

  • Debugger: this tab is divided into the following areas:
  • Elements: appears if you are using Chrome browser for debugging.

  • Debug Output: shows messages sent by your application to the debug output, e.g. with the Debug.WriteLine() method.

  • Parallel Stacks: shows threads and their stack frames on the diagram.

Each area has a context menu that allows you to configure its behavior and navigate between tabs.

Each of the tabs and areas can be hidden/restored, or moved to a location of your choice.

JetBrains Rider: Debug window

Debug toolbar

Item

Tooltip and Shortcut

Description

icons actions restart svg

Rerun
Ctrl+Shift+F5

Click this button to stop the current application and run it again.

icons actions resume svg

Resume Program
F5

When an application is paused, click this button to resume program execution.

icons actions pause svg

Pause Program
Ctrl+Pause

Click this button to pause program execution.

icons actions suspend svg

Stop
Shift+F5

Click this button to terminate the current process.

icons debugger viewBreakpoints svg

View Breakpoints
Ctrl+Alt+B

Click this button to open the Breakpoints dialog where you can configure breakpoints behavior.

icons debugger muteBreakpoints svg

Mute Breakpoints

Use this button to toggle breakpoints status.

You can temporarily mute all the breakpoints in a project to execute the program without stopping at breakpoints.

icons debugger restoreLayout svg

Restore Layout

Click this button to abandon changes to the current layout and return to the default state.

icons general gearPlain svg

Show Options Menu

Click this button to open the menu with the following options available:
  • Show Values Inline: select this option to enable the Inline Debugging feature that allows viewing the values of variables right next to their usage in the editor.

  • Sort Values Alphabetically: select this option to sort the values in the Variables pane in the alphabetical order.

  • Unmute Breakpoints on Session Finish: select this option to re-enable all disabled breakpoints after the debugging session has been finished.

icons general pin tab svg

Pin Tab

Click this button to pin or unpin the current tab. You may need to pin a tab to prevent it from closing automatically when the maximum number of tabs is reached in this window.

Stepping toolbar

Item

Tooltip and Shortcut

Description

icons debugger showCurrentFrame svg

Show Execution Point
Alt+NumPad *

Click this button to highlight the current execution point in the editor and show the corresponding stack frame in the Frames pane.

icon jump to statement

Jump to Statement
Ctrl+Shift+Alt+F9

Sometimes, you may want to skip a part of code without actually executing it (e.g., to avoid a known bug) or to return to a statement that has been already executed. This can be done by forcibly setting the next statement at the current line — use the Jump to statement icon jump to statement command (Ctrl+Shift+Alt+F9) that is also available in the Run menu.

Important notes:

  • Statements between the old and the new execution points are not executed.

  • It is impossible to set the next statement in another function.

  • When moving backwards, the already executed statements are not undone.

icons actions traceOver svg

Step Over
F10

Click this button to execute the program until the next line in the current method or file, skipping the methods referenced at the current execution point (if any). If the current line is the last one in the method, execution steps to the line executed right after this method.

icons debugger actions force step over svg

Force Step Over
Shift+Alt+F8

Click this button to have the debugger step over the method even if this method has breakpoints inside.

icons actions traceInto svg

Step Into
F11

Click this button to have the debugger step into the method called at the current execution point.

icons debugger smartStepInto svg

Smart Step Into
Shift+F7

If the current line contains several nested calls, JetBrains Rider lets you choose a call to step into. Consider the following code line:

Console.WriteLine(Foo(Bar("input") + Baz("input")));
The line contains several calls and if you use Step Into, the debugger will first step into the implementation of Bar(), then into the implementation of Baz() and so on.

If you want to choose which of the calls should be stepped into, for example, Bar(), you can use Smart Step Into icons debugger smartStepInto svg (Shift+F7):

JetBrains Rider: Smart step into - stepping into selected call

When you choose the function to step into, the debugger will set the execution pointer at the first statement of the selected function.
The selector also shows you which of the calls were already executed and allows you to execute these calls again.

icons actions stepOut svg

Step Out
Shift+F11

Click this button to have the debugger step out of the current method, to the line executed right after it.

icons actions runToCursor svg

Run to Statement
Ctrl+F10

Click this button to resume program execution and pause until the execution point reaches the line at the current cursor location in the editor. No breakpoint is required. Actually, there is a temporary breakpoint set for the current line at the caret, which is removed once program execution is paused. Thus, if the caret is positioned at the line which has already been executed, the program will be just resumed for further execution, because there is no way to roll back to previous breakpoints. This action is especially useful when you have stepped deep into the methods sequence and need to step out of several methods at once.

If there are breakpoints set for the lines that should be executed before bringing you to the specified line, the debugger will pause at the first encountered breakpoint.

icons debugger actions force run to cursor svg

Force Run to Statement
Ctrl+Alt+F9

If there are breakpoints between the current execution point and the cursor location, you can force the debugger to skip these breakpoints with the Force Run to Statement icons debugger actions force run to cursor svg command (Ctrl+Alt+F9).

icons debugger evaluateExpression svg

Evaluate Expression
Alt+F8

Click this button to evaluate expressions.

Moving tabs and areas

If you are unhappy with the default layout of the Debug tool window, you can always move the tabs and areas. To to that, just drag a tab or an area to the desired location. The possible target gets highlighted.

Drop the tab or area in the highlighted location.

To restore the default layout of tabs and area, click icons debugger restoreLayout svg in the Debug toolbar.

Last modified: 4 October 2018