From owner-freebsd-threads@FreeBSD.ORG Thu Jun 26 17:21:57 2003 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 F3A7E37B401 for ; Thu, 26 Jun 2003 17:21:56 -0700 (PDT) Received: from pop018.verizon.net (pop018pub.verizon.net [206.46.170.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26F4543FD7 for ; Thu, 26 Jun 2003 17:21:56 -0700 (PDT) (envelope-from mtm@identd.net) Received: from kokeb.ambesa.net ([138.88.140.205]) by pop018.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030627002155.UEBC11703.pop018.verizon.net@kokeb.ambesa.net>; Thu, 26 Jun 2003 19:21:55 -0500 Date: Thu, 26 Jun 2003 20:21:54 -0400 From: Mike Makonnen To: Marcel Moolenaar In-Reply-To: <20030626203624.GA37317@dhcp01.pn.xcllnt.net> References: <3EFB2E12.3080504@intalio.com> <20030626203624.GA37317@dhcp01.pn.xcllnt.net> 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 pop018.verizon.net from [138.88.140.205] at Thu, 26 Jun 2003 19:21:54 -0500 Message-Id: <20030627002155.UEBC11703.pop018.verizon.net@kokeb.ambesa.net> cc: freebsd-threads@FreeBSD.org Subject: Re: libkse / libthr bugs? 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: Fri, 27 Jun 2003 00:21:57 -0000 On Thu, 26 Jun 2003 13:36:24 -0700 Marcel Moolenaar wrote: > On Thu, Jun 26, 2003 at 10:32:02AM -0700, Alex Boisvert wrote: > > > > I written a small test case (see source below), which I've run against > > both libkse and libthr. I'm using -CURRENT as of last Tuesday and > > running on a Dual Athlon MP 1.2 GHz (Tyan Thunder K7 motherboard). On i386 libthr limits an application to 128 _concurrent_ threads. So, you should check the return value from pthread_create() for EAGAIN, in which case you should retry again. > On ia64 I get the following with libthr (libkse is not completely > ported yet): > > % ./foo2 1000 > [very long list of random "bar #" > : > bar 999 > bar 226 > bar 244 > Thread (_thread_initial:0) already on mutexq > Fatal error 'Illegal call from signal handler' at line 1347 in file > /nfs/freebsd/5.x/src/lib/libthr/thread/thr_mutex.c (errno = 0) Great! I've been waiting for this message to appear for some time. Do you have a backtrace by any chance? If not, that's Ok, even without it the program is simple enough that I know where to start looking. > Note that I don't have any of David's signal code patches applied. Any unbreaking of signals in the kernel would definitely help libthr. 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