public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* gcc 10.5: libsanitizer: fsanitize=leak option Issue
@ 2024-04-29 12:07 Estner, Michael
  0 siblings, 0 replies; only message in thread
From: Estner, Michael @ 2024-04-29 12:07 UTC (permalink / raw)
  To: gcc

Hello,

I upgrade the gcc in my setup from 10.2 to 10.5 to the latest commit.

After that I build an application with the -fsanitize=leak option.
The execution of the application stops immediatly after start with the
following error:
CHECK failed:
../../../../src/libsanitizer/lsan/lsan_interceptors.cpp:53
((!lsan_init_is_running)) != (0) (0, 0)

I did some research and found following Issue discussion on Github:
https://github.com/magma/magma/issues/15279

There is as well a solution describe to overwrite __lsan_init() call
with an own, empty, implementation. This is not feasible for me,
because I need to check the applicaitons with the fsanitizer=leak.

There is as well a bug ticket of the error at the ubuntu launch pad:
https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/2038386

The solutions to upgrade to gcc 11 or downgrade to gcc 10.2 are not
feasible for me. I did as well research on the commits from gcc to find
a solution, but could not find a patch, that points directly to that
Issue. In the bug ticket from Ubuntu they say that the: "dlopen-
specific allocator was reimplemented".

Does anyone had experience with that Issue and knows a solution?

Thanks in advance

BR

Michael 

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2024-04-29 12:07 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-04-29 12:07 gcc 10.5: libsanitizer: fsanitize=leak option Issue Estner, Michael

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).