You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when an unhandled exception occurs in the debugger dnSpy displays both the exception type and message. This is a rather limited set of information that could be extended.
Ideas of information that could be added to the exception error prompt:
HResult - Shows the HResult associated with the thrown exception.
InnerException - A lot of the exceptions defined by the core library can have an inner exception. This information would be especially useful for identifying the cause of these exceptions.
StackTrace - This could be helpful but this is not really necessary as the method in which the exception is thrown is automatically shown by dnSpy and the call stack can be inspected through the respective debugger window.
The text was updated successfully, but these errors were encountered:
Displaying HResult property of an unhandled exception is now implemented for both debugging engines. Displaying inner exceptions will require some public API changes to be implemented so it will not make it into 6.2.0.
Currently when an unhandled exception occurs in the debugger dnSpy displays both the exception type and message. This is a rather limited set of information that could be extended.
Ideas of information that could be added to the exception error prompt:
The text was updated successfully, but these errors were encountered: