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

Application crash on startup when upgraded to grpc 1.67.1 #38374

Open
SaurabhGrade opened this issue Jan 2, 2025 · 0 comments
Open

Application crash on startup when upgraded to grpc 1.67.1 #38374

SaurabhGrade opened this issue Jan 2, 2025 · 0 comments

Comments

@SaurabhGrade
Copy link

We are using grpc 1.4.7 and application was working fine. We upgraded to grpc 1.67.1 and facing application crash on startup.

Used below commands to build grpc 1.4.7 earlier
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=../../release ../..
make
make check
make install
To build grpc 1.67.1, below mentioned commands are used :-
cmake3 -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=../../release ../..
make
make check
make install

Detailed description of application crash issue:-

What version of gRPC and what language are you using?
1.67.1

What operating system (Linux, Windows,...) and version?
Linux Red Hat Enterprise Linux 8.9 (Ootpa)

What runtime / compiler are you using (e.g. python version or version of gcc)
gcc version 8.5.0 20210514 (Red Hat 8.5.0-20) (GCC)

What did you do?
Please provide either 1) A unit test for reproducing the bug or 2) Specific steps for us to follow to reproduce the bug. If there’s not enough information to debug the problem, gRPC team may close the issue at their discretion. You’re welcome to re-open the issue once you have a reproduction.
Application crash on startup

What did you expect to see?
no crash

What did you see instead?
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
E0000 00:00:1735642414.694859 2653013 :-1] Metric name grpc.xds_client.resource_updates_valid has already been registered.

Program received signal SIGABRT, Aborted.
Aborted (core dumped)
 
(gdb)
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007fed4857fe65 in __GI_abort () at abort.c:79
#2  0x00000000008425b0 in grpc_core::Crash(absl::lts_20240116::string_view, grpc_core::SourceLocation) ()
#3  0x0000000000b9f881 in grpc_core::GlobalInstrumentsRegistry::RegisterInstrument(grpc_core::GlobalInstrumentsRegistry::ValueType, grpc_core:: absl::lts_20240116::string_view, absl::lts_20240116::string_view, absl::lts_20240116::string_view, bool, absl::lts_20240116::Span<absl::lts_200116::Span<absl::lts_20240116::string_view const>) ()
#4  0x0000000000bc961f in grpc_core::GlobalInstrumentsRegistry::RegistrationBuilder<(grpc_core::GlobalInstrumentsRegistry::ValueType)2, (grpc_cType)1, 3ul, 0ul>::Build() ()
#5  0x000000000086bc6f in __static_initialization_and_destruction_0(int, int) [clone .constprop.383] ()
#6  0x00000000013de66d in __libc_csu_init ()
#7  0x00007fed48598778 in __libc_start_main (main=0x875ea9 <main(int, char**)>, argc=1, argv=0x7ffe8b817478, init=0x13de620 <__libc_csu_init>,
    rtld_fini=, stack_end=0x7ffe8b817468) at ../csu/libc-start.c:270
#8  0x000000000087595e in _start ()
(gdb)

Made the code changes in the libprotobuf.cmake and libprotobuf-lite.cmake files by setting CXX_VISIBILITY_PRESET flag from hidden to default and compiled the static libraries with all the symbols exported.
    Compilation was successful but still getting the same error as above.
 
Compiled GRPC libraries with the compiler flag -fno-delete-null-pointer-checks and also compiled OpenSSL libraries shipped with the grpc third party code. But still the problem remains same.
cmake3 -DCMAKE_BUILD_TYPE=Release -DgRPC_CARES_PROVIDER=module -DBUILD_SHARED_LIBS=OFF -DCMAKE_CXX_FLAGS=-fno-delete-null-pointer-checks -DCMAKE_INSTALL_PREFIX=../../release ../..

Referred : #38158 but didn't get any solution.

Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).

See TROUBLESHOOTING.md for how to diagnose problems better.

Anything else we should know about your project / environment?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants