This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RFC: Re: [patch] Fix for 'info threads' crashes if zombie threads exist
- From: Jan Kratochvil <lace at jankratochvil dot net>
- To: gdb-patches at sourceware dot org
- Cc: Daniel Jacobowitz <drow at false dot org>, Christoph Bartoschek <bartoschek at or dot uni-bonn dot de>
- Date: Tue, 20 Jun 2006 19:04:51 +0200
- Subject: RFC: Re: [patch] Fix for 'info threads' crashes if zombie threads exist
- References: <200606191719.00530.bartoschek@or.uni-bonn.de> <200606201542.12070.bartoschek@or.uni-bonn.de> <20060620135351.GA9853@host0.dyn.jankratochvil.net> <200606201821.41941.bartoschek@or.uni-bonn.de> <200606191719.00530.bartoschek@or.uni-bonn.de> <200606201456.57681.bartoschek@or.uni-bonn.de> <20060620130932.GA21490@nevyn.them.org> <200606201524.45099.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