-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can exchndl be made to catch RaiseFailFastException? #64
Comments
I hope this helps. |
Thanks for the suggestions. Given these options I think I will patch Qt's behaviour for now and consider moving to a catchsegv-like approach in the future. I've always wanted to implement a better UI on crash, so maybe I will try to make a fancier GUI version of it (not now though 😆 ). I tried catchsegv on Krita and didn't see any slowdown on initialization... but frankly Krita on Windows already starts up way slower than on Linux (10 seconds vs 3 seconds). Side note: When I tested with catchsegv, it didn't seem to be able to produce line number info (exchndl outputs them fine). I have split debug file linked with gnu-debuglink, maybe that is broken with catchsegv? |
It should work. |
No further action planned from DrMinGW side, so closing. |
Qt decided that its fatal error handler should call
RaiseFailFastException
instead of justabort
(context). This issue also touches on the exceptional behaviour ofabort
which Qt is trying to prevent.However,
exchndl
is apparently unable to dump the stack trace when the Qt fatal error handler is called. Are there any tricks to makeexchndl
work for this case?The text was updated successfully, but these errors were encountered: