[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 #8 from Kostya Serebryany <konstantin.s.serebryany at gmail dot com> ---
(In reply to Rich Felker from comment #7)
> There's no reason to ask libc for the moving end of the stack; 

There are few other reasons for us, at least for non-main threads:
- we need to know the stack boundaries to correctly report the thread id on 
stack buffer overflow
- we need to unpoison the shadow memory that corresponds the the thread's stack
at thread shutdown
- probably some more less important


> simply &local
> for any automatic variable "local" will do the job. Only the other end of
> the stack needs to be known by your code, and it never changes.

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