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
MM-27887: set traceback to crash from code #15274
Conversation
Unless we set traceback level to crash, goroutines from all threads aren't printed. See: golang/go#13161. This is important because SIGQUIT traces will miss on goroutines. https://mattermost.atlassian.net/browse/MM-27887
golang/go#13161 mentions that after outputting the stacks it aborts when GOTRACEBACK=crash. I couldn't find any mention of that being changed. Do you know if this is still the behaviour? Ok, I see it raises SIGABRT. That will trigger core dump and exit. I guess that's the best we can hope for. |
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.
LGTM
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.
Thanks, this is fine to merge without manual QA.
This change will cause the service to crash with a coredump instead of just dumping the stack trace to console. |
Unless we set traceback level to crash, goroutines from all threads aren't printed. See: golang/go#13161. This is important because SIGQUIT traces will miss on goroutines. https://mattermost.atlassian.net/browse/MM-27887
Unless we set traceback level to crash, goroutines from all threads aren't printed.
See: golang/go#13161.
This is important because SIGQUIT traces will miss on goroutines.
https://mattermost.atlassian.net/browse/MM-27887