From owner-freebsd-bugs@FreeBSD.ORG Mon Feb 21 03:50:22 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 E140616A4CE for ; Mon, 21 Feb 2005 03:50:22 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF64D43D48 for ; Mon, 21 Feb 2005 03:50:22 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j1L3oMPp044945 for ; Mon, 21 Feb 2005 03:50:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j1L3oMTn044944; Mon, 21 Feb 2005 03:50:22 GMT (envelope-from gnats) Date: Mon, 21 Feb 2005 03:50:22 GMT Message-Id: <200502210350.j1L3oMTn044944@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Greg 'groggy' Lehey" 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: Greg 'groggy' Lehey List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Feb 2005 03:50:23 -0000 The following reply was made to PR gnu/77818; it has been noted by GNATS. From: Greg 'groggy' Lehey To: Sean Farley Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: gnu/77818: GDB locks in wait4() when running applications Date: Mon, 21 Feb 2005 14:12:45 +1030 --3O1VwFp74L81IIeR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sunday, 20 February 2005 at 19:15:01 -0600, Sean Farley wrote: > >> Synopsis: GDB locks in wait4() when running applications > >> Description: > > Whenever I run an application through the system's GDB, GDB locks in > wait4(). It does not matter if the application has debugging > information or not. /bin/ls will lock GDB up for me until I type > Ctrl-C. Is this an SMP system? > Two systems of mine exhibit this behavior. One has the binary > nvidia driver with a lot of changes in libmap.conf. The other is > headless without a libmap.conf. I've found something similar with SMP systems only. It wasn't as consistent as the way you describe, and I was able to work around the problem by turning off all but one CPU. See kern/77537 for more details. Greg -- See complete headers for address and phone numbers. --3O1VwFp74L81IIeR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFCGVi1IubykFB6QiMRAn1DAKCHmVcC9GzWgPlsgJTQ7CgfvZ/fcQCgiBfS oTVYzEkdypz0f8S2Hbe5iY4= =AIOY -----END PGP SIGNATURE----- --3O1VwFp74L81IIeR--