[Bug libc/16291] feature request: provide simpler ways to compute stack and tls boundaries

["konstantin.s.serebryany at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16291

--- Comment #45 from Kostya Serebryany <konstantin.s.serebryany at gmail dot com> ---
I've created https://sourceware.org/glibc/wiki/ThreadPropertiesAPI ,
it has more questions than answers; please comment.

FTR, Editing the wiki remains painful due to frequent timeouts. :( 


(In reply to Rich Felker from comment #44)
> Kostya, there are only two ways dynamic TLS can be destroyed: either a
> thread exiting 

Properly catching thread exit is a challenge by itself, 
Today we are using yet another hack to catch thread exit -- I wonder
if you could suggest a better approach. 
I added a relevant section to the wiki page above.

> or a call to dlclose. 

When dlclose happens in one thread, we need to do something with DTLS in 
all threads, which is tricky, if at all possible, w/o knowing 
how exactly glibc itself handles this case. 
hook-based approach will not have this problem,

> Simply hooking these two events will
> allow you to keep track of all destruction even if you're limited to a
> probe-based (rather than hook-based) API.

-- 
You are receiving this mail because:
You are on the CC list for the bug.