glibc 2.19 - asyn-signal safe TLS and ASan.
Kostya Serebryany
kcc@google.com
Wed Jan 29 09:48:00 GMT 2014
[text only]
> Indeed so, thanks!
> So, exporting __signal_safe_memalign&co will allow us to extend the
> existing hack to 2.19.
> If this simple change can not be done for 2.19, can *anything* be done at all?
> (Long term we'd still prefer something less hackish)
FTR, I've implemented an even-uglier-then-before hack that deals with
dynamic TLS in both <=2.18 and 2.19.
So, we will survive the 2.19 release.
But I would appreciate if we can resolve
https://sourceware.org/bugzilla/show_bug.cgi?id=16291
before the next one (2.20).
More information about the Libc-alpha
mailing list