On Apr 28, 2014, at 13:02 , Ken Thomases wrote:
> I've seen this discussed before, but I don't remember where. One of the
> Apple engineers acknowledged the issue. This check is not done (or not
> effective) if the semaphore is created with a value of 0.
It was here, a few months ago. I was
On Apr 28, 2014, at 2:53 PM, Jens Alfke wrote:
> Looks like a dispatch_semaphore intentionally crashes (a sort of assertion
> failure) on deletion if its current value is less than its initial value.
> … semaphores don’t want to be disposed while their current value is less than
> the initial v
Looks like a dispatch_semaphore intentionally crashes (a sort of assertion
failure) on deletion if its current value is less than its initial value. The
crash is an EXC_BAD_INSTRUCTION in _dispatch_semaphore_dispose:
0x7fff896cb279: leaq 0x1037b(%rip), %rcx ; "BUG IN CLIENT OF
LIBDISPA