Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Michael Snyder <msnyder@redhat.com>,
	Roland McGrath <roland@redhat.com>,
	gdb@sources.redhat.com
Subject: Re: libthread_db thread handles
Date: Tue, 14 Jan 2003 23:20:00 -0000	[thread overview]
Message-ID: <20030114232032.GA3774@nevyn.them.org> (raw)
In-Reply-To: <3E249864.2060600@redhat.com>

On Tue, Jan 14, 2003 at 11:08:20PM +0000, Ulrich Drepper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Daniel Jacobowitz wrote:
> 
> > First of all, libthread_db doesn't necessarily create the
> > td_thrhandle_t; they're allocated by the caller of libthread_db, for
> > map_id2thr and map_lwp2thr.  The iterators create them and then throw
> > them away, of course.
> 
> ...which is why you cannot reply on the addresses of these objects to
> have any relevance.  This is why I mentioned it.

OK.  I understand; I don't expect the addresses to be relevant.

> > td_thrhandle_t is opaque; it is documented as opaque in <thread_db.h>. 
> > I don't want to look at th_unique.  Can I rely on the fact that the contents
> > of a td_thrhandle_t are stable and can be re-used if I save the
> > td_thrhandle_t?
> 
> In the current implementation this is the case but I don't want to
> commit to this unless you can show me there are big benefits.  It would
> help if you could describe what functions you see being used often and
> in which contexts.  There are things in the libthread_db implementation
> which can be changed without breaking the ABI.  We just need to know how
> you use the library.

To find the state of a thread, we need to first get a thread handle for
it and only then can we call td_thr_get_info.  I'd like to save a copy
of the td_thrhandle_t when we get the TD_CREATE event, and be able to
hand it to td_thr_get_info until I see a TD_DEATH event (can a thread
die without us getting the TD_DEATH event?  Is there some other thing
we should be watching for a thread to vanish?).

This can be a major timesaver, in addition to caching the LWP ID and
holding on to it as long as we know we've got a 1-to-1 mapping (via
not seeing any TD_SWITCHTO/TD_SWITCHFROM).

If you're not comfortable with it, let me know and I'll figure out
whether I can get the same effect another way.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-01-14 23:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030110204624.GA32002@nevyn.them.org>
     [not found] ` <86wulbc29o.fsf@elgar.kettenis.dyndns.org>
     [not found]   ` <20030113214916.GA18517@nevyn.them.org>
     [not found]     ` <3E235404.45568034@redhat.com>
     [not found]       ` <20030114002758.GA30705@nevyn.them.org>
     [not found]         ` <3E24901B.4841796E@redhat.com>
2003-01-14 22:46           ` Daniel Jacobowitz
2003-01-14 23:01             ` Roland McGrath
2003-01-14 23:07               ` Daniel Jacobowitz
2003-01-14 23:08             ` Ulrich Drepper
2003-01-14 23:20               ` Daniel Jacobowitz [this message]
2003-01-14 23:41                 ` Ulrich Drepper
2003-01-14 23:47                   ` Roland McGrath
2003-01-15  0:16                     ` Michael Snyder
2003-01-14 23:56                   ` Daniel Jacobowitz

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=20030114232032.GA3774@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=drepper@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=msnyder@redhat.com \
    --cc=roland@redhat.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