We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Helps to diagnose the root cause of non reproducible crashes.
It should prevent issues like this #772
In the case of receiving SIGSEGV, we should try to recover the stack trace if not already corrupted and print it to somewhere. (stdout? logs?)
By extending signal handler in main.
Yes
The text was updated successfully, but these errors were encountered:
Dump stack trace on crash (Implement #849) (#870)
3b48d8c
* Print stack trace on crash * Printing stack trace is fully functional except for WIN32 * Minor fixes * Minor fixes
Successfully merging a pull request may close this issue.
Feature request
What problem does this feature solve?
Helps to diagnose the root cause of non reproducible crashes.
It should prevent issues like this
#772
What does the proposed API look like?
In the case of receiving SIGSEGV, we should try to recover the stack trace if not already corrupted and print it to somewhere. (stdout? logs?)
How should this be implemented in your opinion?
By extending signal handler in main.
Are you willing to work on this yourself?
Yes
The text was updated successfully, but these errors were encountered: