#strange lsan problem

1 messages · Page 1 of 1 (latest)

random night
#

I'm getting this error on gcc (--version shows gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0) with the command gcc -Wall -std=c99 -fsanitize=leak -o test3 a2_question3.c a2_question2.c
running test3 throws the error:
==2358740==Sanitizer CHECK failed: ../../../../src/libsanitizer/lsan/lsan_interceptors.cpp:53 ((!lsan_init_is_running)) != (0) (0, 0)
which, I have no clue what means and the only useful search result is an obscure gcc bug https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/2038386

Launchpad
Bug #2038386 “gcc -fsanitize=leak crashes immediately” : Bugs : gcc...

The Leak Sanitizer in the gcc version bundled with Ubuntu 20.04.6 LTS has a fatal issue that makes the compiled program crash immediately (even before main()) with:

==28797==Sanitizer CHECK failed: ../../../../src/libsanitizer/lsan/lsan_interceptors.cpp:53
  ((!lsan_init_is_running)) != (0) (0, 0)

This can be exercised even with a trivial pr...

halcyon nymphBOT
#

When your question is answered use !solved to mark the question as resolved.

Remember to ask specific questions, provide necessary details, and reduce your question to its simplest form. For tips on how to ask a good question run !howto ask.

steel citrus
#

The linked bug mentions that the fix is in gcc 11+. As a workaround you could try using valgrind instead of libsan