From owner-freebsd-threads@FreeBSD.ORG  Fri Apr  4 08:39:17 2003
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
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 0B9A137B401
	for <freebsd-threads@freebsd.org>;
	Fri,  4 Apr 2003 08:39:17 -0800 (PST)
Received: from speicher.org (sirius.speicher.org [209.74.10.51])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AAF4E43FCB
	for <freebsd-threads@freebsd.org>;
	Fri,  4 Apr 2003 08:39:15 -0800 (PST)
	(envelope-from geoff@speicher.org)
Received: from localhost (geoff@localhost)
	by speicher.org (8.11.6/8.11.6) with ESMTP id h34Gp5N05398;
	Fri, 4 Apr 2003 11:51:05 -0500 (EST)
	(envelope-from geoff@speicher.org)
Date: Fri, 4 Apr 2003 11:51:05 -0500 (EST)
From: "Geoffrey C. Speicher" <geoff@speicher.org>
To: Gordon Tetlow <gordont@gnf.org>
In-Reply-To: <20030403234932.GW69100@roark.gnf.org>
Message-ID: <Pine.BSF.4.05.10304041150010.5378-100000@speicher.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-threads@freebsd.org
Subject: Re: 1:N threading
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2003 16:39:17 -0000

On Thu, 3 Apr 2003, Gordon Tetlow wrote:

> On Thu, Apr 03, 2003 at 06:56:44PM -0500, Geoffrey C. Speicher wrote:
> > 
> > I'm going to give it a whirl since Jeff's overnight commits to
> > libthr make my system reboot every time I run mozilla.  How much
> > worse can libpthread be?  :)
> 
> I had a similar problem. There was a recent commit to fix a buffer
> overflow. Give it a try.

Nope, same deal.  And to answer my questions about libpthread, it reboots
much sooner than that.  :)

Geoff