From owner-freebsd-bugs@FreeBSD.ORG Fri May 13 05:50:08 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 CB32316A4CE for ; Fri, 13 May 2005 05:50:08 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B730443D81 for ; Fri, 13 May 2005 05:50:08 +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 j4D5o8HN033022 for ; Fri, 13 May 2005 05:50:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j4D5o89s033021; Fri, 13 May 2005 05:50:08 GMT (envelope-from gnats) Date: Fri, 13 May 2005 05:50:08 GMT Message-Id: <200505130550.j4D5o89s033021@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, 13 May 2005 05:50:08 -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, 13 May 2005 00:47:41 -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-1997951983-1115963261=:7235 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE I think I may have found the issue or at least an issue. It has to do with signal suspensions not being copied from the initial process down to a grandchild. This causes the parent to miss the SIGCHLD when the process exits too quickly. I have an example program[1] to illustrate the problem. This program does work as expected on FreeBSD-4.10 and Linux. Se=E1n 1. http://www.farley.org/freebsd/tmp/grandparent.c --=20 sean-freebsd@farley.org --0-1997951983-1115963261=:7235--