From: David Rothenberger <daveroth@acm.org>
To: cygwin@cygwin.com
Subject: Re: STC for libapr1 failure
Date: Mon, 29 Aug 2011 17:09:00 -0000 [thread overview]
Message-ID: <4E5BC7C0.9020504@acm.org> (raw)
In-Reply-To: <20110829135435.GA31869@calimero.vinschen.de>
On 8/29/2011 6:54 AM, Corinna Vinschen wrote:
> On Aug 27 15:27, David Rothenberger wrote:
>> 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.
>
> I made a couple more changes to the file locking code to accommodate
> POSIX locks as well. Please test the today's developer snapshot,
> which I'm just creating.
The latest baseline fixes my STC and the libpr1 test suite. Thanks!
--
David Rothenberger ---- daveroth@acm.org
The Beatles:
Paul McCartney's old back-up band.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-08-29 17:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 0:39 David Rothenberger
2011-08-26 11:16 ` Corinna Vinschen
2011-08-27 20:37 ` Corinna Vinschen
2011-08-27 22:27 ` David Rothenberger
2011-08-29 13:55 ` Corinna Vinschen
2011-08-29 17:09 ` David Rothenberger [this message]
2012-02-14 8:00 David Rothenberger
2012-02-14 8:07 ` David Rothenberger
2012-02-14 14:03 ` Corinna Vinschen
2012-02-14 14:46 ` Corinna Vinschen
2012-02-14 17:58 ` David Rothenberger
2012-02-14 18:25 ` Corinna Vinschen
2012-02-14 21:43 ` David Rothenberger
2012-02-15 15:39 ` Corinna Vinschen
2012-02-15 19:39 ` David Rothenberger
2012-02-15 20:46 ` Corinna Vinschen
2012-02-15 21:16 ` David Rothenberger
2012-02-15 21:20 ` Corinna Vinschen
2012-02-15 22:14 ` David Rothenberger
2012-02-16 14:11 ` Corinna Vinschen
2012-02-16 15:57 ` David Rothenberger
2012-02-16 16:06 ` Corinna Vinschen
2012-02-18 21:52 ` David Rothenberger
2012-02-20 14:19 ` Corinna Vinschen
2012-02-20 20:15 ` David Rothenberger
2012-02-21 1:29 ` Yaakov (Cygwin/X)
2012-02-21 8:59 ` Corinna Vinschen
2012-02-21 17:10 ` Corinna Vinschen
2012-02-23 14:20 ` Corinna Vinschen
2012-02-23 18:43 ` Achim Gratz
2012-02-24 3:49 ` Yaakov (Cygwin/X)
2012-02-24 8:15 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E5BC7C0.9020504@acm.org \
--to=daveroth@acm.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).