X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 29 Aug 2011 15:54:35 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: STC for libapr1 failure Message-ID: <20110829135435.GA31869@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4E56EB24 DOT 5000505 AT acm DOT org> <20110826111509 DOT GH10490 AT calimero DOT vinschen DOT de> <20110827203706 DOT GA15411 AT calimero DOT vinschen DOT de> <4E596F50 DOT 3050205 AT acm DOT org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4E596F50.3050205@acm.org> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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