This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.25 seems to have broken AddressSaniitzer Inbox x glibc x sanitizer x
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Konstantin Serebryany <konstantin dot s dot serebryany at gmail dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 20 Feb 2018 12:33:57 -0800
- Subject: Re: glibc 2.25 seems to have broken AddressSaniitzer Inbox x glibc x sanitizer x
- Authentication-results: sourceware.org; auth=none
- References: <CAGQ9bdyZDj6gs6G3h2gQ2UyWVMHpuYi3SU0zyJKfGDumP3hJTA@mail.gmail.com>
On Tue, Feb 20, 2018 at 12:24 PM, Konstantin Serebryany
<konstantin.s.serebryany@gmail.com> wrote:
> Hi,
>
> Users are reporting that the fresh glibc breaks AddressSanitizer (asan)
> and probably other sanitizers too.
>
> https://bugs.llvm.org/show_bug.cgi?id=36065
> https://bugs.llvm.org/show_bug.cgi?id=36326
> https://github.com/google/sanitizers/issues/914
>
> The problem seems to be in the new way the dynamic TLS is allocated.
> The current implementation in asan is hackish and a few years back
> we discussed a better one
> (https://sourceware.org/glibc/wiki/ThreadPropertiesAPI)
> but the discussion has stalled.
>
> Can this be addressed in 2.25? At lest the dtls side?
>
> Even if we put another set of hacks into the sanitizers to support 2.25,
> the new glibc will break things for those who use older GCC or LLVM versions.
>
FWIW, sanitizer tests in GCC pass on x86 with glibc 2.26.
--
H.J.