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).
On Mon, Jan 27, 2014 at 7:47 PM, Kostya Serebryany <[email protected]> wrote: > On Mon, Jan 27, 2014 at 7:37 PM, Paul Pluzhnikov <[email protected]> > wrote: > > On Mon, Jan 27, 2014 at 5:37 AM, Kostya Serebryany <[email protected]> > wrote: > > > >>> > How do I "export" __signal_safe_memalign? (I/d like to experiment > myself) > >>> You'll need this snippet of above patch: (line 61,5): > >> > >> Paul, I tried this: > >> > >> --- a/elf/Versions > >> +++ b/elf/Versions > >> @@ -62,5 +62,8 @@ ld { > >> > >> # Pointer protection. > >> __pointer_chk_guard; > >> + # for signal safe TLS > >> + __signal_safe_malloc; __signal_safe_free; __signal_safe_memalign; > >> + __signal_safe_realloc; __signal_safe_calloc; > >> } > >> } > >> > >> it did not help: "nm libc.so | grep signal_safe_memalign" is empty. > > > > It probably did. I believe these functions are defined and used in > > 'ld.so', so try 'nm ld.so | grep signal_safe'. > > 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) > > --kcc > > > > > > > -- > > Paul Pluzhnikov > -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
