Exception is an error that occurs in runtime and typically breaks normal execution flow. JetBrains Rider allows you to effectively debug application exceptions: you can explicitly tell the debugger to suspend the program execution when any unhandled exception or an exception of a particular type is thrown. JetBrains Rider stops the execution right after the exception occurs (before any exception handling is run) allowing you to examine program's stack frames.
Debugging unhandled exceptions
JetBrains Rider can break program execution when an unhandled exception is thrown and display the exception popup with the basic info about the exception at the code line that caused this exception. You can continue running the program, or explore more details in the Exception details tool window:
By default, JetBrains Rider does not break at unhandled exceptions. To enable this, select Break on user-unhandled exceptions (.NET/.NET Core only) on the page of JetBrains Rider settings (Ctrl+Alt+S).
To debug an exception of a particular type, you should create a special exception breakpoint. Unlike line breakpoints, exception breakpoints are assigned not to a certain line of code, but to a certain exception type (e.g., in case of C#, it can be any type inherited from the
To add an exception breakpoint
- Do one of the following:
- Choose from the main menu.
- Specify breakpoint properties. Note that if Just my code is enabled, the debugger will suspend the program only in case the exception is thrown by the user code.
Now, once the exception of the specified type is thrown, the debugger suspends execution.