You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 26, 2024. It is now read-only.
I was trying to test the dynamic_load-example with jaeger tracer in libjaegertracing.so and ended up with a segmentation fault. When I tested dynamic_load-example with libopentracing_mocktracer.so then everything worked as expected.
gdb indicated, that the segmentation fault occurs right when libjaegertracing.so tries to create a std::thread that is related to reporting the traces. The problem is solved if I link the dynamic_load-example against -pthread in the CMakeLists.txt:
This is likely a tracing library specific problem but it took a significant amount of time to realize the underlying issue, so would it be reasonable to add -pthread to the CMakeLists.txt
when building on unix?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was trying to test the dynamic_load-example with jaeger tracer in
libjaegertracing.so
and ended up with a segmentation fault. When I tested dynamic_load-example withlibopentracing_mocktracer.so
then everything worked as expected.gdb indicated, that the segmentation fault occurs right when
libjaegertracing.so
tries to create a std::thread that is related to reporting the traces. The problem is solved if I link thedynamic_load-example
against-pthread
in the CMakeLists.txt:This is likely a tracing library specific problem but it took a significant amount of time to realize the underlying issue, so would it be reasonable to add
-pthread
to the CMakeLists.txtwhen building on unix?
The text was updated successfully, but these errors were encountered: