This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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

--- Comment #41 from Sergey Matveev <earthdok at google dot com> ---
(In reply to Rich Felker from comment #39)
> I realize
> this makes a bit more work for tools like ASAN which would rather have
> asynchronous notification (note: they could still get it by intercepting the
> functions that could change the state then calling the query function during
> the intercept)

Doesn't this basically translate to __dl_tls_getaddr(), as far as allocation of
new DTLS blocks is concerned? It's the only function that we can intercept, and
it's a hot one. If we take this approach, we'll need a fast way to check
whether our record needs updating before performing a full query. Something as
simple as a function which returns the current DTV's generation counter should
work, I think?

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]