Bug#203434: libc6: accessing thread-local storage causes SIGSEGV

[Denis Barbier <barbier@linuxfr.org>]

[Daniel Jacobowitz]
>> My understanding is that while GCC has to generate the right code,
>> thread-local storage also requires support from the linker, run-time
>> loader, and C library.  I'm reporting this against libc6 on the
>> assumption that either libc itself or the loader (/lib/ld-2.3.1.so) is
>> at fault.  It's possible, though, that the problem is elsewhere.
>>
>> For the record, I'm also using binutils 2.14.90.0.5-0.1 and gcc 3.3-2,
>> all on Debian unstable.
> 
> You are correct that our glibc has this support disabled.  A future
> version will have it enabled.
> 
> However, on some architectures, including i686, I believe that it also
> requires kernel support.  Hmm, reading it again perhaps that's not
> true.

It looks like this bug has been fixed in libc6 2.3.5, can it be closed?

Denis