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
On Tue, Feb 20, 2018 at 12:33 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> 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.
They are passing the GCC tests, which I bet are not complete.
(In fact, it's just a totally different test suite)
>From https://bugs.llvm.org/show_bug.cgi?id=36065:
The failing tests are:
LeakSanitizer-AddressSanitizer-x86_64 :: TestCases/Linux/use_tls_dynamic.cc
LeakSanitizer-Standalone-x86_64 :: TestCases/Linux/use_tls_dynamic.cc
...
MemorySanitizer-X86_64 :: dtls_test.c
...
These are the DTLS tests.
--kcc
>
>
> --
> H.J.