This is the mail archive of the
mailing list for the Cygwin project.
Re: STC for libapr1 flock failure
- From: David Rothenberger <daveroth at acm dot org>
- To: cygwin at cygwin dot com
- Date: Wed, 15 May 2013 11:52:04 -0700
- Subject: Re: STC for libapr1 flock failure
- References: <517AAA86 dot 9030506 at acm dot org> <517AE610 dot 9040506 at acm dot org> <5181A3E8 dot 3040501 at acm dot org>
David Rothenberger wrote:
> David Rothenberger wrote:
>> On 4/26/2013 9:25 AM, David Rothenberger wrote:
>>> This was working the last time I built libapr1 (19-Feb-2012).
>> The test case does work with 1.7.17-1. The last snapshot I could find
>> where it worked is 2012-12-18 17:38:50 UTC. The 2012-12-21 snapshot
>> broke it badly, causing
>> wait_sig: WaitForSingleObject(0x6C8) for thread exit returned 258
>> messages on even the first iteration. Subsequent snapshots just hang
>> after a few iterations.
> I retested the STC with the latest snapshot and it still hangs.
> I know Christopher didn't say it might be fixed, but since there were
> signal handler changes involved I thought I'd give it a try.
There hasn't been any response to the bug report yet and I'm wondering
why. I don't want to be pushy, but I'm curious if this is because core
developers haven't yet had time to look at it, the STC does not provide
enough information, or perhaps it was just overlooked.
I'm trying to build a 64-bit version of this library and the test case
is failing there, too. If this won't be addressed, I will disable flock
locking in libapr1.
David Rothenberger spammer? -> firstname.lastname@example.org
GPG/PGP: 0x7F67E734, C233 365A 25EF 2C5F C8E1 43DF B44F BA26 7F67 E734
"Those who will be able to conquer software will be able to conquer the
-- Tadahiro Sekimoto, president, NEC Corp.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple