-
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
Improved error handling #184
Labels
Milestone
Comments
Stivius
pushed a commit
to Stivius/xibo-linux
that referenced
this issue
Apr 8, 2020
We print stack trace using boost::stacktrace::stacktrace() which is not the safest way to do it in a signal handler however it gives us more info if compared to safe call. xibosignage#184
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Right now we are spending a lot of time to find out the problem source in case if it's related to segfault or segabort. We need to improve error handling to have more info that could help us to investigate bugs.
Describe the solution you'd like
Add more logs for trace and debug levels, intercept SIGSEGV/SIGABRT signals and print stack trace.
The text was updated successfully, but these errors were encountered: