[bug #25307] [NSConditionLock tryLockWhenCondition:] shouldn't throw exception when lock is unavailable

[Gregory John Casamento]

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

On Mac OS X:
============
2009-01-29 16:24:05.226 locktest[4344:10b] ======== SINGLE THREADED TESTS
2009-01-29 16:24:05.229 locktest[4344:10b] [NSLock lock] test passed -- Mac
OS X behavior is to deadlock in this case, we throw an exception.
2009-01-29 16:24:05.230 locktest[4344:10b] [NSConditionLock lock] test passed
-- Mac OS X behavior is to deadlock in this case, we throw an exception.
2009-01-29 16:24:05.230 locktest[4344:10b] [NSRecursiveLock lock] test
passed
2009-01-29 16:24:05.231 locktest[4344:10b] [NSLock tryLock] test passed
2009-01-29 16:24:05.232 locktest[4344:10b] [NSConditionLock tryLock] test
passed
2009-01-29 16:24:05.233 locktest[4344:10b] [NSRecursiveLock tryLock] test
passed
2009-01-29 16:24:05.233 locktest[4344:10b] ======== MULTI THREADED TESTS

NOTE: For the first two cases, I had to make them pass since throwing an
exception is basically equivalent to letting them deadlock.  I'm wondering if
we should also allow them to deadlock in those cases.

The same code on GNUstep:
=========================
2009-01-29 16:36:35.890 LockTest[30778] ======== SINGLE THREADED TESTS
2009-01-29 16:36:35.891 LockTest[30778] [NSLock lock] test passed
2009-01-29 16:36:35.891 LockTest[30778] [NSConditionLock lock] test failed
2009-01-29 16:36:35.891 LockTest[30778] [NSRecursiveLock lock] test passed
2009-01-29 16:36:35.891 LockTest[30778] [NSLock tryLock] test passed
2009-01-29 16:36:35.891 LockTest[30778] [NSConditionLock tryLock] test
failed
2009-01-29 16:36:35.892 LockTest[30778] [NSRecursiveLock tryLock] test
passed
2009-01-29 16:36:35.892 LockTest[30778] ======== MULTI THREADED TESTS



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?25307>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/