STC for libapr1 failure

David Rothenberger
Sat Aug 27 22:27:00 GMT 2011

On 8/27/2011 1:37 PM, Corinna Vinschen wrote:
> On Aug 26 13:15, Corinna Vinschen wrote:
>> On Aug 25 17:39, David Rothenberger wrote:
>>> For a while now, the test cases that come with libapr1 have been
>>> bombing with this message:
>>>   *** fatal error - NtCreateEvent(lock): 0xC0000035
>>> I finally took some time to investigate and have extracted a STC
>>> that demonstrates the problem.
>> Thanks a lot for the testcase.  In theory, the NtCreateEvent call should
>> not have happened at all, since it's called under lock, and the code
>> around that should have made sure that the object doesn't exist at the
>> time.
>> After a few hours of extrem puzzlement, I now finally know what happens.
>> It's kinda hard to explain.
[... very good description of flock problem ...]
> Please test the latest snapshot.  It should fix this problem, as well as
> a starvation problem with signals (and, fwiw, thread cancel events) in
> flock, lockf, and POSIX fcntl locks.

The new snapshot runs the flock STC. Thanks!

I've been building libapr1 without F_SETLK support for a while since
it was also triggering the "NtCreateEvent(lock): 0xC0000035"
error. Since you mentioned fcntl, I tried re-enabling the fcntl
mutexes. They still trigger the error.

I've attached a similar STC that uses fcntl instead of flock.

David Rothenberger  ----

"It's what you learn after you know it all that counts."
                -- John Wooden
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: stc-fcntl-fork.c
URL: <>
-------------- next part --------------
Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list