From owner-freebsd-threads@FreeBSD.ORG  Wed Oct 27 23:26:58 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 09D9916A4CE; Wed, 27 Oct 2004 23:26:58 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id DAAEE43D1D; Wed, 27 Oct 2004 23:26:57 +0000 (GMT)
	(envelope-from davidxu@freebsd.org)
Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1])
	i9RNQuZa031859;	Wed, 27 Oct 2004 23:26:57 GMT
	(envelope-from davidxu@freebsd.org)
Message-ID: <41802EE5.6070200@freebsd.org>
Date: Thu, 28 Oct 2004 07:27:33 +0800
From: David Xu <davidxu@freebsd.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.7.2) Gecko/20041004
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Daniel Eischen <deischen@freebsd.org>
References: <Pine.GSO.4.43.0410271826590.239-100000@sea.ntplx.net>
In-Reply-To: <Pine.GSO.4.43.0410271826590.239-100000@sea.ntplx.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: threads@freebsd.org
cc: John Baldwin <jhb@freebsd.org>
Subject: Re: Infinite loop bug in libc_r on 4.x with condition variables and
 signals
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, 27 Oct 2004 23:26:58 -0000

Daniel Eischen wrote:

>> FWIW, we are having (I think) the same problem on 5.3 with 
>> libpthread. The
>>
>>panic there is in the mutex code about an assertion failing because a thread
>>is on a syncq when it is not supposed to be.
>>    
>>
>
>David and I recently fixed some races in pthread_join() and
>pthread_exit() in -current libpthread.  Don't know if those
>were responsible...
>
>  
>
That fix should be MFCed ASAP.

>Here's a test program that shows correct behavior with both
>libc_r and libpthread in -current.
>
>  
>