From: Roland McGrath <roland@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
Michael Snyder <msnyder@redhat.com>,
gdb@sources.redhat.com
Subject: Re: libthread_db thread handles
Date: Tue, 14 Jan 2003 23:47:00 -0000 [thread overview]
Message-ID: <200301142346.h0ENkp512697@magilla.sf.frob.com> (raw)
In-Reply-To: Ulrich Drepper's message of Tuesday, 14 January 2003 15:40:54 -0800 <3E24A006.4070703@redhat.com>
> If you have the pthread_t value computing the td_thrhandle_t is an
> operation which can be performed entirely without the looking at the
> inferior. At least in the new implementation. Just call
> td_ta_map_id2thr(). This shouldn't add any measurable overhead.
>
> I would prefer you caching the pthread_t value very much over caching
> any opaque data structure. If this means adding a function
> td_ta_map_thr2id() I'd have no problems with it. But not even this
> should be necessary since for both events, TD_CREATE and TD_DEATH, the
> eventdata is the pthread_t value. And this should be a documented
> interface.
One can already use td_thr_get_info and ti_tid is the pthread_t value (that
can be given to td_ta_map_id2thr).
next prev parent reply other threads:[~2003-01-14 23:47 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
2003-01-14 23:41 ` Ulrich Drepper
2003-01-14 23:47 ` Roland McGrath [this message]
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=200301142346.h0ENkp512697@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=msnyder@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