Date: Fri, 20 May 2005 18:50:05 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: <200505201850.j4KIo5KZ089205@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, 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200505201850.j4KIo5KZ089205>