From owner-freebsd-bugs@FreeBSD.ORG Fri May 20 18:50:05 2005 Return-Path: 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 DCF6E16A4CE for ; Fri, 20 May 2005 18:50:05 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B923243DAD for ; Fri, 20 May 2005 18: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 j4KIo53Y089206 for ; Fri, 20 May 2005 18: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 j4KIo5KZ089205; Fri, 20 May 2005 18:50:05 GMT (envelope-from gnats) Date: Fri, 20 May 2005 18:50:05 GMT Message-Id: <200505201850.j4KIo5KZ089205@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: =?ISO-8859-1?Q?Se=E1n_C=2E_Farley?= Subject: Re: gnu/77818: GDB locks in wait4() when running applications X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 20 May 2005 18:50:06 -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: bug-followup@FreeBSD.org, sean-freebsd@farley.org Cc: Subject: Re: gnu/77818: GDB locks in wait4() when running applications Date: Fri, 20 May 2005 13:49:13 -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-116671042-1116614953=:42991 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE I am using 5.4-STABLE with sources from May 15th's: FreeBSD thor.farley.org 5.4-STABLE FreeBSD 5.4-STABLE #0: Sun May 15 01:46:56 CDT 2005 root@thor.farley.org:/usr/obj/usr/src/sys/THOR i386 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=3D/bin/sh gdb a.out), the parent will be stuck waiting for a signal it will never receive in sigsuspend(). 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. Se=E1n 1. http://www.farley.org/freebsd/tmp/parent.c --=20 sean-freebsd@farley.org --0-116671042-1116614953=:42991--