This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: STC for libapr1 failure
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 14 Feb 2012 15:02:40 +0100
- Subject: Re: STC for libapr1 failure
- References: <4F3A14A8.4090506@acm.org>
- Reply-to: cygwin at cygwin dot com
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?
Btw., mmap is really simple. For your testcase that could be, for
instance:
#include <sys/mman.h>
void init_shm ()
{
x = mmap (NULL, getpagesize (), PROT_READ | PROT_WRITE,
MAP_SHARED | MAP_ANONYMOUS, -1, 0);
if (!x)
{
perror ("mmap failed");
exit (1);
}
}
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