Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <lace@jankratochvil.net>
To: gdb-patches@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>,
	        Christoph Bartoschek <bartoschek@or.uni-bonn.de>
Subject: RFC: Re: [patch] Fix for 'info threads' crashes if zombie threads exist
Date: Tue, 20 Jun 2006 17:05:00 -0000	[thread overview]
Message-ID: <20060620170451.GA17022@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <200606201821.41941.bartoschek@or.uni-bonn.de> <20060620132737.GA21951@nevyn.them.org> <20060619165609.GA14691@host0.dyn.jankratochvil.net>

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.


Thanks for any info,
Jan Kratochvil


On Mon, 19 Jun 2006 18:56:09 +0200, Jan Kratochvil wrote:
> Hi,
> 
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182116
> 
> Steps to Reproduce:
> 1.Start print-threads within GDB
> 2.Set a breakpoint in __pthread_unwind
> 3.Run the program
> 4.When the program stops at the breakpoint, run `info threads'
> 
> 
> Patch disables handling of the TD_DEATH notification from __nptl_death_event()
> and tries to keep the thread in TD_THR_ZOMBIE state as long as possible before
> its LWP ceases to be. While expecting regressions so far no such was found,
> statistically it improves some testcases (+24 passes,-14 fails), no negatives.
> ('longjmp' part not resolved; not reproducible for GDB-CVS)
> 
> Thread is now debuggable through pthread_exit(3) and the thread terminating
> code.
> 
> 
> 
> Regards,
> Jan Kratochvil


  reply	other threads:[~2006-06-20 17:05 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                 ` Jan Kratochvil [this message]
2006-06-20 17:11                   ` RFC: " Daniel Jacobowitz
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=20060620170451.GA17022@host0.dyn.jankratochvil.net \
    --to=lace@jankratochvil.net \
    --cc=bartoschek@or.uni-bonn.de \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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