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
Save backtrace to file on panic #1681
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, thank you! 🎉
I forgot to tell you this, and it doesn't seem like it's stated anywhere visible, so here I go: Should you contribute here or somewhere else, please consider creating another branch than main
for your changes, and PR from that branch to this main
. This makes local testing setups less messy, for a lengthier explanation see #1468 (comment).
Looks good to me! I'd leave it bit-rot a day or two, then get it in. |
Choooooo chooooooooooo! Thank you! |
Co-authored-by: MultisampledNight <contact@multisamplednight.com>
What kind of change does this PR introduce?
Did this PR introduce a breaking change?
A breaking change includes anything that breaks backwards compatibility either at compile or run time.
I added a panic hook that appends the backtrace to a log file in the current directory so that there is some clue as to what happened when neovide crashes.
It works by attaching a panic hook at the beginning of
main()
. The original main function has been moved toprotected_main()
. I moved it here for now as I was not sure how to integrate the hook intomain()
's documentation.