Received-SPF: pass (google.com: domain of yselkowitz@gmail.com designates 10.50.203.66 as permitted sender) client-ip=10.50.203.66;
Message-ID: <1329787780.8088.2.camel@YAAKOV04>
Subject: Re: STC for libapr1 failure
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin@cygwin.com
Date: Mon, 20 Feb 2012 19:29:40 -0600
In-Reply-To: <20120220141749.GA27701@calimero.vinschen.de>
References: <20120215153851.GQ25918@calimero.vinschen.de>	 <4F3C09D9.6000406@acm.org> <20120215204521.GB27454@calimero.vinschen.de>	 <4F3C208B.2060007@acm.org> <20120215212010.GA4183@calimero.vinschen.de>	 <4F3C2E35.3080308@acm.org> <20120216140932.GI19092@calimero.vinschen.de>	 <4F3D2748.8080205@acm.org> <20120216160458.GK19092@calimero.vinschen.de>	 <4F401D73.7010908@acm.org> <20120220141749.GA27701@calimero.vinschen.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Mon, 2012-02-20 at 15:17 +0100, Corinna Vinschen wrote:
> As always, thanks for the testcase.  I think I found the problem.  It's
> hard to explain if you don;t know how the code works, but it boils down
> to the fact that my last round of patches back in August were not
> actually fixing the problem, but only working around it.  I'm hopeful
> that I got it right this time.  I'm just generating a new snapshot.
> Please give it another hit with the APR testsuite.

I'm sorry to report that the 20120220 snapshot breaks the X server,
which uses fcntl() with a lock file.


Yaakov


--
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