From owner-freebsd-threads@FreeBSD.ORG Sun Jun 29 20:51:37 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 B338D37B401 for ; Sun, 29 Jun 2003 20:51:37 -0700 (PDT) Received: from pop015.verizon.net (pop015pub.verizon.net [206.46.170.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id C291043FCB for ; Sun, 29 Jun 2003 20:51:36 -0700 (PDT) (envelope-from mtm@identd.net) Received: from kokeb.ambesa.net ([138.88.32.7]) by pop015.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030630035135.WEWF20810.pop015.verizon.net@kokeb.ambesa.net>; Sun, 29 Jun 2003 22:51:35 -0500 Date: Sun, 29 Jun 2003 23:51:34 -0400 From: Mike Makonnen To: Marcel Moolenaar In-Reply-To: <20030630030106.GA1345@athlon.pn.xcllnt.net> References: <20030630030106.GA1345@athlon.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 pop015.verizon.net from [138.88.32.7] at Sun, 29 Jun 2003 22:51:35 -0500 Message-Id: <20030630035135.WEWF20810.pop015.verizon.net@kokeb.ambesa.net> cc: threads@freebsd.org Subject: Re: Regression in libthr on ia64 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: Mon, 30 Jun 2003 03:51:38 -0000 On Sun, 29 Jun 2003 20:01:06 -0700 Marcel Moolenaar wrote: > It doesn't matter if I compile with -DWITH_SLEEP or not. > > Is this a known issue? Is there some work in progress still? > 2nd question first: yes, there is still more work to be done, but committed bits should be self-contained and not break anything. Did you update both your kernel and libthr together? when? There was a window of opportunity (several hours) yesterday where the interface to sigtimedwait was changed but libthr was not. Also, is it possible to narrow down the time frame during which it broke? It seems strange; however, that a statically linked executable would behave differently. 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