From owner-freebsd-threads@FreeBSD.ORG Tue Apr 12 20:43:46 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 8467D16A4CE; Tue, 12 Apr 2005 20:43:46 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C07A43D39; Tue, 12 Apr 2005 20:43:46 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.30.114.143]) by comcast.net (rwcrmhc13) with ESMTP id <2005041220434401500grsjje>; Tue, 12 Apr 2005 20:43:45 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost.127.in-addr.arpa [127.0.0.1])j3CKhctB004298; Tue, 12 Apr 2005 16:43:39 -0400 (EDT) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)j3CKhcaq004297; Tue, 12 Apr 2005 16:43:38 -0400 (EDT) (envelope-from rodrigc) Date: Tue, 12 Apr 2005 16:43:37 -0400 From: Craig Rodrigues To: David Xu Message-ID: <20050412204337.GA4277@crodrigues.org> References: <200504111210.j3BCAZmU002870@freefall.freebsd.org> <425B02BB.5060904@freebsd.org> <20050412071220.GA17393@stack.nl> <425B866C.4010609@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <425B866C.4010609@freebsd.org> User-Agent: Mutt/1.5.9i 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 20:43:46 -0000 On Tue, Apr 12, 2005 at 04:27:24PM +0800, David Xu wrote: > You have to fix it in uthread_fork.c, lock __malloc_lock over > __sys_fork() call. > but why libc_r ? it is depreciated. I know that many us don't like libc_r, ;), but has re@ made an official announcement about deprecating it? Until that happens, then libc_r will still remain in the tree, and people will use (and complain about) it. > 6.0-Release is the time to drop its support and move it to ports. :) Sounds good to me.....has re@ agreed to it? The sooner we can remove old crufty threading libraries from FreeBSD, the happier many of us will be! -- Craig Rodrigues rodrigc@crodrigues.org