-
Notifications
You must be signed in to change notification settings - Fork 440
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
crash in ext::http::client::curl::HttpOperation::Send #1220
Comments
@ZDzhao Can you share a bit more context on this :
Ideally, fd/socket buffer-overflow shouldn't happen, as the Export is sequential i.e, next export will be initiated only after the previous export is completed. So there is shouldn't be more than one socket connection open at a given time. Would be interesting to understand the scenario here. |
This issue was marked as stale due to lack of activity. It will be closed in 7 days if no furthur activity occurs. |
Closed as inactive. Feel free to reopen if this is still an issue. |
Same here. |
Could you please test async-changes? |
Same here. Test with SDK v1.2.0 and using OTLP HTTP export. Env: gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5) Code: Stack:
|
Close as #1413 is merged |
Enviroment: CentOS Linux release 7.3.1611 (Core)
#0 0x00007ff6ee439a37 in abort () from /lib64/libc.so.6
#1 0x00007ff6ee477f47 in __libc_message () from /lib64/libc.so.6
#2 0x00007ff6ee512d87 in __fortify_fail () from /lib64/libc.so.6
#3 0x00007ff6ee510f40 in __chk_fail () from /lib64/libc.so.6
#4 0x00007ff6ee512cf7 in __fdelt_warn () from /lib64/libc.so.6
#5 0x0000000000d55ed8 in WaitOnSocket (timeout_ms=, for_recv=0, sockfd=3175)
at bazel-out/k8-opt/bin/external/io_opentelemetry_cpp/ext/_virtual_includes/headers/opentelemetry/ext/http/client/curl/http_operation_curl.h:460
#6 opentelemetry::v1::ext::http::client::curl::HttpOperation::Send (this=0x7ff6b4c02d00)
at bazel-out/k8-opt/bin/external/io_opentelemetry_cpp/ext/_virtual_includes/headers/opentelemetry/ext/http/client/curl/http_operation_curl.h:214
#7 0x0000000000d5a3f9 in operator() (__closure=0x7ff3e0f4fc88)
at bazel-out/k8-opt/bin/external/io_opentelemetry_cpp/ext/_virtual_includes/headers/opentelemetry/ext/http/client/curl/http_operation_curl.h:298
#8 __invoke_impl<long int, opentelemetry::v1::ext::http::client::curl::HttpOperation::SendAsync(std::function<void(opentelemetry::v1::ext::http::client::curl::HttpOperation&)>)::<lambda()> > (__f=)
at /usr/local/gcc-7.5/lib/gcc/x86_64-pc-linux-gnu/7.5.0/../../../../include/c++/7.5.0/bits/invoke.h:60
#9 __invoke<opentelemetry::v1::ext::http::client::curl::HttpOperation::SendAsync(std::function<void(opentelemetry::v1::ext::http::client::curl::HttpOperation&)>)::<lambda()> > (__fn=) at /usr/local/gcc-7.5/lib/gcc/x86_64-pc-linux-gnu/7.5.0/../../../../include/c++/7.5.0/bits/invoke.h:96
#10 _M_invoke<0> (this=0x7ff3e0f4fc88) at /usr/local/gcc-7.5/lib/gcc/x86_64-pc-linux-gnu/7.5.0/../../../../include/c++/7.5.0/thread:234
#11 operator() (this=0x7ff3e0f4fc88) at /usr/local/gcc-7.5/lib/gcc/x86_64-pc-linux-gnu/7.5.0/../../../../include/c++/7.5.0/thread:243
#12 operator() (this=0x7ff3971fb720) at /usr/local/gcc-7.5/lib/gcc/x86_64-pc-linux-gnu/7.5.0/../../../../include/c++/7.5.0/future:1339
#13 std::_Function_handler<std::unique_ptr<std::__future_base::_Result_base, std::__future_base::_Result_base::_Deleter> (), std::__future_base::_Task_setter<std::unique_ptr<std::__future_base::_Result, std::__future_base::_Result_base::_Deleter>, std::thread::_Invoker<std::tuple<opentelemetry::v1::ext::http::client::curl::HttpOperation::SendAsync(std::function<void (opentelemetry::v1::ext::http::client::curl::HttpOperation&)>)::{lambda()#1}> >, long> >::_M_invoke(std::_Any_data const&) (__functor=...) at /usr/local/gcc-7.5/lib/gcc/x86_64-pc-linux-gnu/7.5.0/../../../../include/c++/7.5.0/bits/std_function.h:302
#14 0x00000000006146bf in operator() (this=)
at /usr/local/gcc-7.5/lib/gcc/x86_64-pc-linux-gnu/7.5.0/../../../../include/c++/7.5.0/bits/std_function.h:706
same as this question https://stackoverflow.com/questions/22827510/how-to-avoid-bad-fd-set-buffer-overflow-crash
The text was updated successfully, but these errors were encountered: