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 17:11:00 -0000 [thread overview]
Message-ID: <20060620171109.GA28310@nevyn.them.org> (raw)
In-Reply-To: <20060620170451.GA17022@host0.dyn.jankratochvil.net>
On Tue, Jun 20, 2006 at 07:04:51PM +0200, Jan Kratochvil wrote:
> Hi Christoph,
>
> On Tue, 20 Jun 2006 18:21:41 +0200, Christoph Bartoschek wrote:
> ...
> > I applied your patch to gdb 6.4 and do not see the error again.
>
> sincerely thanks for the test.
>
> Is there any objection regarding the patch import? What was the original
> TD_DEATH notification reason? Not sure if the patch is compatible with
> non-Linux platforms.
A little patience, please. It takes a while to review GDB patches,
especially non-obvious ones - and thread-db support seems to be quite
complicated.
TD_DEATH events were supported because there are all sorts of things
which can go wrong when you ask libthread_db about a thread that it
considers dead. At that point, as far as the library is concerned, the
thread is gone. A new thread can be created with the same thread ID -
even before this one exits. If you ask it to map that thread ID to an
LWP, it will refuse. After your patch, I strongly suspect there are
places where you could hit control-c and get mysterious errors from
GDB.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-20 17:11 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 [this message]
2006-06-20 18:54 ` Jan Kratochvil
2006-06-20 19:07 ` Daniel Jacobowitz
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=20060620171109.GA28310@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