From owner-freebsd-bugs@FreeBSD.ORG Wed May 25 15:50:05 2005 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4C1616A41C for ; Wed, 25 May 2005 15:50:05 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C8CD43D1F for ; Wed, 25 May 2005 15:50:05 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j4PFo5bv006802 for ; Wed, 25 May 2005 15:50:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j4PFo5Ms006801; Wed, 25 May 2005 15:50:05 GMT (envelope-from gnats) Date: Wed, 25 May 2005 15:50:05 GMT Message-Id: <200505251550.j4PFo5Ms006801@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: =?ISO-8859-1?Q?Se=E1n_C=2E_Farley?= Cc: Subject: Re: gnu/77818: GDB locks in wait4() when running applications X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ISO-8859-1?Q?Se=E1n_C=2E_Farley?= List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2005 15:50:05 -0000 The following reply was made to PR gnu/77818; it has been noted by GNATS. From: =?ISO-8859-1?Q?Se=E1n_C=2E_Farley?= To: David Xu Cc: bug-followup@freebsd.org Subject: Re: gnu/77818: GDB locks in wait4() when running applications Date: Wed, 25 May 2005 10:41:14 -0500 (CDT) This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-237620714-1117035674=:1320 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Wed, 25 May 2005, David Xu wrote: >> I have a new test program[1] that I think shows the problem. My >> previous program actually showed another bug that has since been >> fixed. Actually, it shows two problems. When run within the >> debugger (SHELL=3D3D/bin/sh gdb a.out), the parent will be stuck >> waiting for a signal it will never receive in sigsuspend(). >>=20 > > Please try following patch, I believe the old hack is incorrect now > with jhb's sleep queue. Thank you, thank you! That fixes my bug. >> The other problem is that nanosleep() is exiting immediately with a >> return of zero although the time to sleep has not passed. To see it >> do this, remove the BROKEN_NANOSLEEP_WITHIN_GDB definition at the top >> of the program and recompile. >> > > This is a long history bug, I believe it is still in RELENG_4. Now the > bug is in kern_sig.c: do_tdsignal(), when process is being debugged, a > masked signal can wake up a sleeping thread! that's why it is broken. Is it fixable? Should I open a PR for it, or is there one already? Se=E1n --=20 sean-freebsd@farley.org --0-237620714-1117035674=:1320--