Re: tls, valgrind gdbserver and qGetTLSAddr

[Siddhesh Poyarekar <siddhesh at redhat dot com>]

On Thu, Aug 07, 2014 at 12:07:13AM +0200, Philippe Waroquiers wrote:
> On Wed, 2014-08-06 at 17:17 +0400, Konstantin Serebryany wrote:
> > This question rings the bell...
> > https://sourceware.org/ml/libc-alpha/2014-04/msg00313.html
> > https://sourceware.org/glibc/wiki/ThreadPropertiesAPI
> 
> Yes, there are similarities in some of the needs.
> There are also some differences, e.g. Valgrind observes
> most of what happens by intercepting or wrapping syscalls
> or glibc calls (eg pthread creation or dead) and
> Valgrind (at least currently) is also not supposed to call any
> library to do its work (this is why valgrind cannot use
> libthread_db).

But then isn't calling into glibc to get the offset better than having
to hardcode it?

Of course, the ThreadPropertiesAPI is still evolving as an idea and it
would be awesome to have all diagnostic tools that need it (gdb,
valgrind, *san), give feedback to the design.  Oh yeah, and if someone
volunteers to hack it up, that would be even better :)

Siddhesh

Attachment: pgpaBbxzUbMp8.pgp
Description: PGP signature