This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: tls, valgrind gdbserver and qGetTLSAddr
- From: Konstantin Serebryany <konstantin dot s dot serebryany at gmail dot com>
- To: Siddhesh Poyarekar <siddhesh at redhat dot com>
- Cc: Philippe Waroquiers <philippe dot waroquiers at skynet dot be>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Wed, 13 Aug 2014 11:51:30 -0700
- Subject: Re: tls, valgrind gdbserver and qGetTLSAddr
- Authentication-results: sourceware.org; auth=none
- References: <1407183880 dot 2180 dot 33 dot camel at soleil> <CAGQ9bdxSZU-3CrqEc9RuYGZiKNisCBv1xQnP=24iJDBEHtZKeg at mail dot gmail dot com> <1407362833 dot 2189 dot 29 dot camel at soleil> <20140813104003 dot GR9284 at spoyarek dot pnq dot redhat dot com>
On Wed, Aug 13, 2014 at 3:40 AM, Siddhesh Poyarekar <siddhesh@redhat.com> wrote:
> 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 :)
I am ready to implement ThreadPropertiesAPI in glibc, but only after
there is agreement on the interface.
>
> Siddhesh