From: Daniel Jacobowitz <drow@false.org>
To: Jan Kratochvil <lace@jankratochvil.net>
Cc: gdb-patches@sourceware.org,
Christoph Bartoschek <bartoschek@or.uni-bonn.de>
Subject: Re: RFC: Re: [patch] Fix for 'info threads' crashes if zombie threads exist
Date: Tue, 20 Jun 2006 19:07:00 -0000 [thread overview]
Message-ID: <20060620190740.GA31643@nevyn.them.org> (raw)
In-Reply-To: <20060620185326.GA9482@host0.dyn.jankratochvil.net>
On Tue, Jun 20, 2006 at 08:53:26PM +0200, Jan Kratochvil wrote:
> > A new thread can be created with the same thread ID - even before this one
> > exits.
>
> Not sure of how much are non-Linux platforms a concern for these minor issues.
Hint: the file was renamed a while back to "linux-thread-db.c".
> Apparently on Linux kernel the same LWP id cannot be created until the final
> syscall __NR_exit.
No, that's the LWP id. In linux-thread-db.c things are still indexed
by thread ID, which is a pointer in NPTL - and NPTL will aggressively
reuse them.
I think the real fix to this problem is going to involve less
dependence on thread IDs. I've been migrating the code away from that
and I'll try to find some time in the next week to finish the job;
maybe that will help.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-20 19:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200606191719.00530.bartoschek@or.uni-bonn.de>
[not found] ` <200606201542.12070.bartoschek@or.uni-bonn.de>
[not found] ` <20060620135351.GA9853@host0.dyn.jankratochvil.net>
[not found] ` <200606201821.41941.bartoschek@or.uni-bonn.de>
[not found] ` <200606201456.57681.bartoschek@or.uni-bonn.de>
[not found] ` <20060620130932.GA21490@nevyn.them.org>
[not found] ` <200606201524.45099.bartoschek@or.uni-bonn.de>
[not found] ` <20060620132737.GA21951@nevyn.them.org>
2006-06-19 16:56 ` Jan Kratochvil
2006-06-20 17:05 ` RFC: " Jan Kratochvil
2006-06-20 17:11 ` Daniel Jacobowitz
2006-06-20 18:54 ` Jan Kratochvil
2006-06-20 19:07 ` Daniel Jacobowitz [this message]
2006-07-13 4:01 ` Daniel Jacobowitz
2006-07-13 13:28 ` Jan Kratochvil
2006-07-13 13:43 ` Daniel Jacobowitz
2006-07-13 15:07 ` Jan Kratochvil
2006-07-13 18:50 ` Mark Kettenis
2006-07-13 19:47 ` Daniel Jacobowitz
2006-07-13 23:16 ` Mark Kettenis
2006-07-18 22:55 ` Daniel Jacobowitz
2006-07-14 13:15 ` Christoph Bartoschek
2006-07-14 13:36 ` 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=20060620190740.GA31643@nevyn.them.org \
--to=drow@false.org \
--cc=bartoschek@or.uni-bonn.de \
--cc=gdb-patches@sourceware.org \
--cc=lace@jankratochvil.net \
/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