X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=L8TTeDSbUAfownSHBUFpBRIGCWYX8CTgGZBk9r4xzI4EZ3HnnS3N4
	t+eccdTNb7YH2icBHrij0HhzBANmtCaab/Y3+qzYwNo1tTzYdT+CECGbp+xyqFNX
	egwD3eRyBcSV1tGxt38D1QxwGrtLydcUaPiJzln6HgtofIPR0pcA0U=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=MuRdCoetvA8z5GYFVubhNimHX8Y=; b=XdvbqsTgZ8AP7leox3etOZR/oNJ8
	atw29R+M7Rlxm7ZiU0k0h0HL13ou+67N/PImbe2aapTqlRehF7WKVnPuMDUbq+dL
	KDRGzNbUt7dBD8tSoH2wZFy2cEmXfvFaKc5CpxVdzuuGn0vF3m/Cf37wP74iXKqs
	ZsU5q488BRVRHi4=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status:	No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1//CoYrt9J3kKk773bN2o9W
Date:	Thu, 16 May 2013 01:38:00 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: STC for libapr1 flock failure
Message-ID:	<20130516053800.GA7448@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<517AAA86 DOT 9030506 AT acm DOT org> <517AE610 DOT 9040506 AT acm DOT org> <5181A3E8 DOT 3040501 AT acm DOT org> <5193D954 DOT 20207 AT acm DOT org>
MIME-Version:	1.0
In-Reply-To:	<5193D954.20207@acm.org>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Wed, May 15, 2013 at 11:52:04AM -0700, David Rothenberger wrote:
>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.

My time is in very short supply these days so I hadn't had a chance to
look into this.  I just did now, however.  This should be fixed in the
next snapshot (building now).

http://cygwin.com/snapshots/

Thanks for the test case.

cgf

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

- Raw text -