From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mark.kettenis@xs4all.nl, dje@google.com, gdb@sourceware.org
Subject: Re: improved thread id reporting
Date: Sat, 04 Apr 2009 22:17:00 -0000 [thread overview]
Message-ID: <20090404212114.GA3077@caradoc.them.org> (raw)
In-Reply-To: <834ox4cfz2.fsf@gnu.org>
On Sat, Apr 04, 2009 at 11:37:53PM +0300, Eli Zaretskii wrote:
> > Date: Sat, 4 Apr 2009 15:21:32 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: dje@google.com, gdb@sourceware.org
> >
> > I think the existing IDs are quite handy.
>
> What for? If they are useful, we should probably tell in the manual
> how to use them.
Their meaning is platform-specific; they're usually something that
will be recognized by programmers familiar with the OS in question.
On native Linux, they're the same as pthread_self would return.
I think they're just LWP IDs when using gdbserver; we had trouble
passing NPTL thread IDs over the remote protocol.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-04-04 21:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 19:06 Doug Evans
2009-04-04 19:07 ` Mark Kettenis
2009-04-04 20:40 ` Daniel Jacobowitz
2009-04-04 21:21 ` Eli Zaretskii
2009-04-04 22:17 ` Daniel Jacobowitz [this message]
2009-04-05 1:11 ` Doug Evans
2009-04-05 3:42 ` Eli Zaretskii
2009-04-05 3:48 ` Daniel Jacobowitz
2009-04-05 7:19 ` Paul Pluzhnikov
2009-04-05 18:50 ` Eli Zaretskii
2009-04-05 20:11 ` Paul Pluzhnikov
2009-04-05 20:36 ` Eli Zaretskii
2009-04-04 22:35 ` Doug Evans
2009-04-06 2:58 ` Doug Evans
2009-04-06 3:33 ` Eli Zaretskii
2009-04-06 15:36 ` Mark Kettenis
2009-04-06 20:21 ` Eli Zaretskii
2009-04-06 7:39 ` Daniel Jacobowitz
2009-04-06 21:21 ` Eli Zaretskii
2009-05-08 5:43 ` Doug Evans
2009-04-06 20:20 ` Tom Tromey
2009-04-06 20:20 ` Eli Zaretskii
2009-04-06 22:15 ` Tom Tromey
2009-04-07 15:18 ` Doug Evans
2009-04-04 22:24 ` Doug Evans
2009-04-05 3:13 ` Daniel Jacobowitz
2009-04-05 9:16 ` Mark Kettenis
2009-04-05 18:23 ` Eli Zaretskii
2009-04-05 19:22 ` Doug Evans
2009-04-04 19:20 ` Thiago Jung Bauermann
2009-04-04 19:21 ` Eli Zaretskii
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=20090404212114.GA3077@caradoc.them.org \
--to=drow@false.org \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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