From owner-freebsd-threads@FreeBSD.ORG  Wed Nov  3 12:04:51 2004
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 5DC4F16A4CE; Wed,  3 Nov 2004 12:04:51 +0000 (GMT)
Received: from lara.cc.fer.hr (lara.cc.fer.hr [161.53.72.113])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 9CA8843D49; Wed,  3 Nov 2004 12:04:48 +0000 (GMT)
	(envelope-from ivoras@fer.hr)
Received: from [127.0.0.1] (localhost.cc.fer.hr [127.0.0.1])
	by lara.cc.fer.hr (8.13.1/8.13.1) with ESMTP id iA3C4Bim022004;
	Wed, 3 Nov 2004 13:04:11 +0100 (CET)
	(envelope-from ivoras@fer.hr)
Message-ID: <4188C93B.2010209@fer.hr>
Date: Wed, 03 Nov 2004 13:04:11 +0100
From: Ivan Voras <ivoras@fer.hr>
User-Agent: Mozilla Thunderbird 0.8 (X11/20041021)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John Baldwin <jhb@freebsd.org>
References: <200411021712.11115.jhb@FreeBSD.org>
In-Reply-To: <200411021712.11115.jhb@FreeBSD.org>
X-Enigmail-Version: 0.85.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit
cc: threads@freebsd.org
Subject: Re: More mono + libpthread breakage..
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: Wed, 03 Nov 2004 12:04:51 -0000

John Baldwin wrote:
> It looks like libpthread is not calling _cond_wait_backout() when a thread 
> gets a signal after calling thr_sched_switch() from pthread_cond_wait().  

Glad to see the issue was not abandoned! I only understood a fraction of 
this, so is it something that could be fixed soon? (Maybe even, 
hopefully, for 5.3-release? :)) )