[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #25307] [NSConditionLock tryLockWhenCondition:] shouldn't throw exc

From: Richard Frith-Macdonald
Subject: [bug #25307] [NSConditionLock tryLockWhenCondition:] shouldn't throw exception when lock is unavailable
Date: Fri, 30 Jan 2009 12:11:24 +0000
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; en-us) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/3.2.1 Safari/525.27.1

Follow-up Comment #14, bug #25307 (project gnustep):

I put the tests in the testsuite, ran it on MacOS-X, and checked the results,
then changed the case of NSConditionLock-tryLock in GNUstpe to match the
behavior in MacOS-X.

I noticed the comments about MacOS-X deadlocking for NSConnectonLock
attempting to lock recursively.  That was already flagged in the testsuite for
NSLock as a MacOS-X bug.
However, when I consider it, I don't think the MacOS-X behavior is totally
stupid  ... perhaps we should mimic MacOS-X and halt the thread in this
situation rather than raising an exception.   Does it make sense to allow an
application to deadlock a thread and (perhaps) have other threads continue


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]