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

Attach backtraces explicitly in error logging #25569

Merged
merged 1 commit into from
Jan 17, 2018
Merged

Conversation

c42f
Copy link
Member

@c42f c42f commented Jan 15, 2018

To avoid ambiguity and confusion, do not assume that catch_backtrace()
is the backtrace associated with a logged exception. Instead, always
attach the backtrace explicitly.

I think this is the best way to address @JeffBezanson's comment at #25370 (comment). I believe #19979 can be fixed, but that won't address the potential for ambiguity in not attaching the backtrace explicitly. I'm not thrilled about the extra boilerplate, but it might be best for now.

To avoid ambiguity and confusion, do not assume that `catch_backtrace()`
is the backtrace associated with a logged exception. Instead, always
attach the backtrace explicitly.
@c42f c42f merged commit d548bf9 into master Jan 17, 2018
@c42f c42f deleted the cjf/logging-backtraces branch January 17, 2018 01:10
@c42f c42f added the logging The logging framework label Jan 17, 2018
Keno pushed a commit that referenced this pull request Jun 5, 2024
Attach backtraces explicitly in error logging
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
logging The logging framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants