This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: STC for libapr1 failure

On Feb 14 09:58, David Rothenberger wrote:
> On 2/14/2012 6:45 AM, Corinna Vinschen wrote:
> > On Feb 14 15:02, Corinna Vinschen wrote:
> >> On Feb 14 00:00, David Rothenberger wrote:
> >>> The libapr1 test cases are failing again for flock locks. This same
> >>> test case failed with 1.7.9 with a fatal error[1], but that was
> >>> corrected. The test is no longer encountering the fatal error, but
> >>> it is producing the wrong result.
> >>
> >> Thanks for the testcase.  I think I found the issue.  An event handle
> >> was closed in the wrong place, outside of the important mutex lock for
> >> the lock object.  I applied the patch to CVS.  Your testcase now appears
> >> to run fine for me.  Can you try your entire testsuite again and see
> >> if there's another failure lurking?
> > 
> > I uploaded a snapshot for testing.
> Thanks. The snapshot fixes the flock test case, but now the fcntl test
> case is failing.

*Sob*.  How so?  Does it hang or does it allow multiple concurrent
exclusive locks as the flock case?

> I'll try to send an STC for that case, but I suspect the one from last
> year will have the problem.

Please send it anyway.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]