Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 Oct 2004 07:27:33 +0800
From:      David Xu <davidxu@freebsd.org>
To:        Daniel Eischen <deischen@freebsd.org>
Cc:        John Baldwin <jhb@freebsd.org>
Subject:   Re: Infinite loop bug in libc_r on 4.x with condition variables and signals
Message-ID:  <41802EE5.6070200@freebsd.org>
In-Reply-To: <Pine.GSO.4.43.0410271826590.239-100000@sea.ntplx.net>
References:  <Pine.GSO.4.43.0410271826590.239-100000@sea.ntplx.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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.
>
>  
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41802EE5.6070200>