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
stackdriver output plugin broken on arm32v7 docker images since v3.0.0 #8785
Comments
FYI @edsiper @leonardo-albertovich @nokute78 this likely affects any threaded input plugin on this platform, not just fluent-bit/src/flb_output_thread.c Line 329 in 07475e7
Haven't actually run it but the only way a segfault makes sense in this stacktrace is if |
I created a command in gdb to print out stack memory, &dns_ctx, then step into flb_net_dns_lookup_context_cleanup() and print out dns_ctx. The stack memory looks weird right before the seg fault.
|
Bug Report
Describe the bug
The stackdriver output plugin has been broken for arm32v7 release builds (ie. docker images) since v3.0.0.
I have done some digging and this does not seem to occur because of any recently introduced bugs. Instead it seems that previous to this commit: 71746b3 setting FLB_RELEASE=On wouldn't build a release binary unless FLB_DEBUG was also explicitly turned off, so the docker images always included a debug build of fluent-bit until v3.0.0.
To Reproduce
In the core dump output below the stack is corrupted and causes dns_ctx to get the illegal address: 0x17cbb6dd.
Expected behavior
The stackdriver output plugin should work on arm32v7 release build or at least docker images work. I tested and this isn't a problem for arm64 or x86.
Your Environment
Test on:
- Raspbian GNU/Linux 11 (bullseye) (raspberry pi 2b)
- Debian (bullseye) (embedded Linux pc)
Additional context
I have attached valgrind output below:
valgrind-out.txt
I will be falling back to the v2.2 docker image for now.
The text was updated successfully, but these errors were encountered: