[Bug sanitizer/88791] ASAN deadlocks in threaded application

marxin at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Mon Jan 14 19:14:00 GMT 2019


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791

--- Comment #11 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to dominik.strasser from comment #10)
> Looking at the backtrace, the effects are very different between gcc 7.4 and
> 9.0. Making it work on a different glibc wouldn't help for me. CentOs 7.5 ==
> RHEL 7.5 which is the latest "commercial" Linux system. What could we do to
> make it work?

Hm, still, the glibc is really quite old. Anyway, let's try more debugging:

- using the GCC trunk, I would open the application in gdb and step through
GetThreadStackAndTls, please report which line triggers the signal (handled by
your app)? You can build libsanitizer with -O0 which will make debugging more
easier
- you can maybe build newer glibc, install it to a different location and then
use something like LD_PRELOAD to test newer GCC
- you can also -fsanitize=undefined, or -fsanitize=thread in order to test
whether other sanitizer work
- if you trust me, you can contact me personally and provide access to a system
where I can do a debugging

Anyway, I would be happy to help, but it's not so easy without a reproducer ;)


More information about the Gcc-bugs mailing list