Follow-up Comment #6, bug #25307 (project gnustep):
The point of tryLock and tryLockWhenCondition: is to attempt to do
the
lock and return NO, if it can't.
Sure ... but the rationale was that, if the lock is held by the current
thread then calling it is evidence of a probable bug.
In the
Update of bug #25346 (project gnustep):
Status:None = In Progress
___
Follow-up Comment #1:
I rsolved the first retain cycle and cleaned up the code in GSAnimator a bit.
There still might
Follow-up Comment #6, bug #25243 (project gnustep):
Could you please add the back trace for the new segmentation fault as well?
It might just be the same as before, but how should I know...
___
Reply to this item at:
