Date: Wed, 27 Oct 2004 17:55:48 -0700 From: Julian Elischer <julian@elischer.org> To: David Xu <davidxu@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: <41804394.7020306@elischer.org> In-Reply-To: <41802EE5.6070200@freebsd.org> References: <Pine.GSO.4.43.0410271826590.239-100000@sea.ntplx.net> <41802EE5.6070200@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
David, do you have revision numbers of what needs to be MFC'd? David Xu wrote: > 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. >> >> >> > > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to > "freebsd-threads-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41804394.7020306>