-
Notifications
You must be signed in to change notification settings - Fork 417
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
provide a little more information before calling std::terminate #2630
Labels
Comments
github-actions
bot
added
the
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
label
Apr 5, 2024
esigo
added
triage/unresolved
Indicates an issue that can not or will not be resolved.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Apr 8, 2024
I commented out my logging initialization today and logging calls on Linux now:
Logging calls on Mac work just fine before/after. This is the init call I commented out:
|
I have a stacktrace now for the termination call:
|
This issue was marked as stale due to lack of activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I've incorporated OpenTelemetry into my program and on certain execution paths, especially on Linux, I get
terminate called without an active exception
or similar kinds of messages.If I take out my OpenTelemetry initialization/cleanup functions and leave the null Otel spans and logs in there, nothing crashes. I have exception handlers defined, but there are a few cases where a raw std::terminate is called from the library.
For example:
opentelemetry-cpp/api/include/opentelemetry/nostd/span.h
Line 103 in 848db57
I have no idea if this is the bug or not, but it makes it harder. I would expect a library to log something if it's going to call terminate.
The text was updated successfully, but these errors were encountered: