Date: Sun, 31 Oct 2004 03:23:41 -0700 From: Scott Long <scottl@freebsd.org> To: Brian Fundakowski Feldman <green@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libpthread/thread thr_mutex.c Message-ID: <4184BD2D.9030209@freebsd.org> In-Reply-To: <20041031050620.GQ93831@green.homeunix.org> References: <200410310503.i9V53ofj011896@repoman.freebsd.org> <20041031050620.GQ93831@green.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Brian Fundakowski Feldman wrote: > On Sun, Oct 31, 2004 at 05:03:50AM +0000, Brian Feldman wrote: > >>green 2004-10-31 05:03:50 UTC >> >> FreeBSD src repository >> >> Modified files: >> lib/libpthread/thread thr_mutex.c >> Log: >> Make pthread_mutex_trylock(3) return EBUSY on failure, as all software >> packages expect and seems to be most correct according to the slightly- >> ambiguous standards. >> >> MFC after: 1 month >> Corroborated by: POSIX <http://tinyurl.com/4uvub>; >> Reviewed by: silence on threads@ > > > Software such as mozilla projects (using NSPR) and Java have been > broken in various ways by this. We need to try to be more compatible > with the most popular interpretation of the standards (instead of just > inventing our own) -- usually we're pretty good about this. > Please define 'broken'? There are many test suites available for pthreads. How does this affect those test suites, and have you _directly_ talked with those who run the tests suites? Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4184BD2D.9030209>