X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
X-Mail-Handler:	MailHop Outbound by DynDNS
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1+dgx4iMNI71Qvw+uuFr6E5
Date:	Sat, 7 Apr 2012 19:39:46 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [1.7.13] STATUS_ACCESS_VIOLATION when running cygwin programs in NAnt scripts
Message-ID:	<20120407233946.GA27186@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4F7FFF49 DOT 90708 AT andreloker DOT de> <20120407173857 DOT GA22639 AT ednor DOT casa DOT cgf DOT cx> <4F809A44 DOT 8000509 AT andreloker DOT de>
MIME-Version:	1.0
In-Reply-To:	<4F809A44.8000509@andreloker.de>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Sat, Apr 07, 2012 at 09:49:24PM +0200, Andre Loker wrote:
>Am 07.04.2012 19:38, schrieb Christopher Faylor:
>> On Sat, Apr 07, 2012 at 10:48:09AM +0200, Andre Loker wrote:
>>> Hello,
>>>
>>> On a new system with a clean 1.7.13 installation (CYGWIN_NT-6.1-WOW64
>>> rs200313 1.7.13(0.260/5/3) 2012-04-05 12:43 i686 Cygwin) I'm getting
>>> STATUS_ACCESS_VIOLATIONs whenever I try to run any cygwin program as
>>> part of a NAnt* build script.
>>>
>> I have a vague idea.  Try the 2012-04-07 snapshot when it shows up.
>>
>> http://cygwin.com/snapshots/
>I tried the snapshot and it works. Thanks a lot for the quick solution! 
>I feared my error description was a bit too vague to begin with.
>
>Out of interest - how comes that the error only occurred when the 
>programs were run from the build script.

I can only guess but I suspect that something was closing stdin/stdout
and we didn't deal correctly with that.

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 -