-
Notifications
You must be signed in to change notification settings - Fork 296
Error UX Improvements #199
Description
When hitting an error, I noticed myself struggling to parse what was going on. (enough so that I had to switch to VS to figure it out)
First up, a slight issue is I have to scroll sideways to view the full thing,

but even when I view it, it seems to lack information compared to VS (doesn't tell me the location of the access violation)

compared to

The next issue is, at a glance it seems obvious what has happened in VS (memory couldn't be read)

But in raddbg I couldn't figure out what was happening. At first glance I thought the memory was just zeroed, only to realize later that it couldn't be read (hovering over it made things click for me)

This isn't an issue now that I've learnt what's going on, but I figured I'd share the experience anyway since it might be helpful for improving the UX for new users coming from VS.