Date: Fri, 13 May 2005 05:50:08 GMT From: =?ISO-8859-1?Q?Se=E1n_C=2E_Farley?= <sean-freebsd@farley.org> To: freebsd-bugs@FreeBSD.org Subject: Re: gnu/77818: GDB locks in wait4() when running applications Message-ID: <200505130550.j4D5o89s033021@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
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?= <sean-freebsd@farley.org>
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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200505130550.j4D5o89s033021>