Windows crash catcher throws uninformative exceptions
The following discussion from !455 (merged) should be addressed:
-
@elsid started a discussion: (+2 comments) This should report why it's failed. Specifically based on WaitForSingleObject return value it should add the value itself or error message from GetLastError function. The same is for all other exceptions. Otherwise we need to resolve mysteries like:
We should save the return value of WaitForSingleObject
etc., and if it's the one that means an error happened, also call GetLastError
(and potentially convert the error identifier to a human-readable string). The information should then be added to the exception message.