feature: 104792: more helpful Win32 error codes to help track down the CMissile OnMove crash #266
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was sadly unable to figure out what is causing the the CMissile OnMove crash bug (yet) after 4 hours of trying different things to reproduce it., but I made the Win32 error that it throws more useful
Here is an example of what the new error codes look like:
CException: Win32 Error: EXCEPTION_ACCESS_VIOLATION - Operation: READ (0) - ADDR: 0In context it looks like this (Note: this was NOT a reproduction of the issue, I deliberately caused this by nulling out a pointer using the debugger):