From owner-freebsd-threads@FreeBSD.ORG Tue Apr 12 07:12:22 2005 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C060B16A4CE; Tue, 12 Apr 2005 07:12:22 +0000 (GMT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id B34E343D53; Tue, 12 Apr 2005 07:12:21 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id A9C641F1FF; Tue, 12 Apr 2005 09:12:20 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id 888216250; Tue, 12 Apr 2005 09:12:20 +0200 (CEST) Date: Tue, 12 Apr 2005 09:12:20 +0200 From: Marc Olzheim To: David Xu Message-ID: <20050412071220.GA17393@stack.nl> References: <200504111210.j3BCAZmU002870@freefall.freebsd.org> <425B02BB.5060904@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline In-Reply-To: <425B02BB.5060904@freebsd.org> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i cc: Marc Olzheim cc: freebsd-threads@freebsd.org Subject: Re: threads/76690: fork hang in child for (-lc_r & -lthr) X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 07:12:23 -0000 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Apr 12, 2005 at 07:05:31AM +0800, David Xu wrote: > >Confirmed to be b0rken on FreeBSD 4.11's libc_r as well. :-/ > > > >Marc > > > This is no longer true for libthr, I can not close the PR > because it also reports libc_r problem. I know, I didn't ask for it to be closed. :-) Is there any info on where the bug could be ? I could take a look at it... Marc --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCW3TUezjnobFOgrERArUuAKCb3Z0H171YzrJcaweq0z5qBS+q2gCgkHDL dT34N1RyNJROgqqW/VHyLIU= =wPzq -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga--