JetBrains Rider 2021.2 Help

Navigate from stack trace to exception

When you receive an external stack trace (for example, from a bug report), you can open it in the dedicated Stacktrace window and then navigate to code where the corresponding exception originated. In this window, you can click files, types, and methods to display them in the editor.

Each stack trace is opened in a new tab, which stays available until you close it or close the solution. If you close the Stacktrace window, you can reopen it by choosing View | Tool Windows | Stacktrace from the menu.

Navigate to code that caused an exception

  1. Copy exception stack trace to the clipboard.

  2. Press Ctrl+E, T or choose Code | Analyze Stack Trace or Thread Dump... from the main menu. Alternatively, you can press Ctrl+Shift+A, start typing the command name in the popup, and then choose it there.

  3. The Stacktrace window opens displaying the exception stack trace from the clipboard in a new tab.

    Study the stack trace and click highlighted items to display the corresponding code in the editor.

  4. If you prefer to wrap long lines in the stack trace, use the corresponding toolbar button Icons actions toggle soft wrap

Navigating from stack trace to exception

When the code that you are debugging throws an exception, you can click Stack Trace Explorer in the exception popup to study the exception right away or later in the Stacktrace window:

JetBrains Rider: Opening stack trace from exception
Last modified: 30 September 2021