From: Florian Weimer <fweimer@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: Florian Weimer via Gdb <gdb@sourceware.org>
Subject: Re: Accessing pthread_key_create thread-specific data
Date: Fri, 12 Mar 2021 17:00:27 +0100 [thread overview]
Message-ID: <87mtv84b1g.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <87wnuc2wqb.fsf@tromey.com> (Tom Tromey's message of "Fri, 12 Mar 2021 08:54:52 -0700")
* Tom Tromey:
>>>>>> "Florian" == Florian Weimer via Gdb <gdb@sourceware.org> writes:
>
> Florian> We have some functionality in libthread_db in glibc that provides access
> Florian> to pthread_key_create thread-specific data (aka pthread_setspecific and
> Florian> pthread_getspecific). I would like to write a GDB test for this
> Florian> functionality, but I can't find how GDB exposes this data in the UI. Is
> Florian> this just dead code?
>
> As far as I know, these aren't used and I think have never been used.
Thanks for conforming.
> I'm not sure how I would go about exposing this to users. The most
> natural way might be to intercept calls to pthread_*specific. Maybe a
> couple of new convenience functions would be good though, and less
> magical.
>
> I guess this would primarily be useful for core file debugging?
That's a good point. The data structures are not completely trivial to
decode even if you have debuginfo symbols.
I do not plan to work on that. I just had to make some changes on the
glibc side, but I guess I just won't be able to test them.
Thanks,
Florian
next prev parent reply other threads:[~2021-03-12 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 13:00 Florian Weimer
2021-03-12 15:54 ` Tom Tromey
2021-03-12 16:00 ` Florian Weimer [this message]
2021-03-12 16:39 ` Andrew Dinn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtv84b1g.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gdb@sourceware.org \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).