Skip to content
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

Report stack trace in case of crash #849

Closed
m-seker opened this issue Jun 27, 2020 · 0 comments · Fixed by #870
Closed

Report stack trace in case of crash #849

m-seker opened this issue Jun 27, 2020 · 0 comments · Fixed by #870

Comments

@m-seker
Copy link
Contributor

m-seker commented Jun 27, 2020

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

@Paulchen-Panther Paulchen-Panther linked a pull request Jul 9, 2020 that will close this issue
13 tasks
Paulchen-Panther pushed a commit that referenced this issue Jul 12, 2020
* Print stack trace on crash

* Printing stack trace is fully functional except for WIN32

* Minor fixes

* Minor fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants