From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: eliz@gnu.org, gdb@sources.redhat.com
Subject: Re: debugging threaded apps. thread ID missing in corefile.
Date: Sun, 12 Jun 2005 00:47:00 -0000 [thread overview]
Message-ID: <200506120046.j5C0kaOW019775@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20050607131022.GA30174@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 7 Jun 2005 09:10:22 -0400)
Date: Tue, 7 Jun 2005 09:10:22 -0400
From: Daniel Jacobowitz <drow@false.org>
> > Not really. The ID is a pointer above 0x80000000, used by the
> > implementation.
>
> Well, then perhaps we should display the thread ID in hex?
Hmm. I wouldn't object to this. The number is opaque to the user
code; for LinuxThreads it is an encoded index into an array (usually
between 0 and 64k; the first few threads are numbered around 32k and
16k). That looks plausible in hex or in decimal. For NPTL they are
pointers and would look more plausible in hex.
The number isn't really opaque to the user. The numbers have type
`pthread_t' and can be printed by the user when debugging his program.
It's the pthread_t type that is opaque. Ideally we'd use the the
`pthread_t' type for the formatting of these values. But AFAIC hex is
a good default.
Mark
next prev parent reply other threads:[~2005-06-12 0:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 22:29 Program no longer exists [SOLVED] Alvin Beach
2005-06-06 22:42 ` debugging threaded apps. thread ID missing in corefile Manoj Iyer
2005-06-07 0:09 ` Daniel Jacobowitz
2005-06-07 3:46 ` Eli Zaretskii
2005-06-07 13:10 ` Daniel Jacobowitz
2005-06-12 0:47 ` Mark Kettenis [this message]
2005-06-07 0:37 ` Program no longer exists [UNSOLVED] Alvin Beach
2005-06-07 18:45 ` Program no longer exists [SOLVED - 95% sure] Alvin Beach
2005-06-17 11:18 ` Program no longer exists [SOLVED - Completely] Alvin Beach
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=200506120046.j5C0kaOW019775@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sources.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