From owner-freebsd-current@FreeBSD.ORG Thu May 29 14:07:29 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 312C037B401 for ; Thu, 29 May 2003 14:07:29 -0700 (PDT) Received: from out006.verizon.net (out006pub.verizon.net [206.46.170.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 970EF43F75 for ; Thu, 29 May 2003 14:07:22 -0700 (PDT) (envelope-from mtm@identd.net) Received: from kokeb.ambesa.net ([138.88.45.55]) by out006.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030529210716.DVVC25800.out006.verizon.net@kokeb.ambesa.net>; Thu, 29 May 2003 16:07:16 -0500 Date: Thu, 29 May 2003 17:06:52 -0400 From: Mike Makonnen To: Lars Eggert In-Reply-To: <3ED59893.5010301@isi.edu> References: <20030526225111.HVVN25800.out006.verizon.net@kokeb.ambesa.net> <3ED59893.5010301@isi.edu> X-Mailer: Sylpheed version 0.8.10 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [138.88.45.55] at Thu, 29 May 2003 16:07:05 -0500 Message-Id: <20030529210716.DVVC25800.out006.verizon.net@kokeb.ambesa.net> cc: freebsd-current@freebsd.org Subject: Re: Libthr stable enough for testing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2003 21:07:29 -0000 I have committed some changes to libthr today. All but one of them were bug fixes, so I encourage everyone to update their source. On Wed, 28 May 2003 22:20:19 -0700 Lars Eggert wrote: > Mike Makonnen wrote: > > > > Most major locking work in libthr is finished. I believe it is stable > > enough now that it can be used for most applications[1]. I would > > appreciate it if people would try it out and report any bugs. > > I had been running with libc_r symlinked to libthr for a few days with > no problems, and rebuilt some ports during that time. > > The machine (SMP) would sometimes freeze solid (no panic). > I symlinked > libc_r back to the original library, and from then on, starting > gnomepanel and some other gnome pieces would fail due to errors about > libthr. I couldn't find them in any log file right now, but I think I > remember one was about getpwuid_r not being found. (The ports that > caused problems were gnome 2.3 beta ports from the marcuscom CVS tree.) > > From what I understand, libthr should be a drop-in replacement for > libc_r, so I was surprised to see this, but maybe I misunderstood? No, you're right. The ports must have been statically linked. I'll investigate. As for the lockups, libthr by itself should not be able to lockup your machine. I'll investigate when I get back access to the SMP machine. > I'll try to get a dump of the exact error messages when I have access to > the box again in a few days. Please. Cheers. -- Mike Makonnen | GPG-KEY: http://www.identd.net/~mtm/mtm.asc mtm@identd.net | D228 1A6F C64E 120A A1C9 A3AA DAE1 E2AF DBCC 68B9 mtm@FreeBSD.Org| FreeBSD - The Power To Serve