X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RCVD_IN_SORBS_WEB,SPF_HELO_PASS
X-Spam-Check-By:	sourceware.org
From:	"James Johnston" <JamesJ AT motionview3d DOT com>
To:	<cygwin AT cygwin DOT com>
References:	<CAH7x9fdkQZzDiN2DFz05FWFtcJkKHb6YdcSChhyLwjWFQASM7A AT mail DOT gmail DOT com> <CAH7x9fenDwtUxMNbGma=BHVpUUw4+C8JeUYanoQ6HL7sfkY4CQ AT mail DOT gmail DOT com>
In-Reply-To:	<CAH7x9fenDwtUxMNbGma=BHVpUUw4+C8JeUYanoQ6HL7sfkY4CQ@mail.gmail.com>
Subject:	RE: 1.7.15-1: mintty bash failing to run .NET executables ?
Date:	Tue, 22 May 2012 15:49:55 -0000
Message-ID:	<007a01cd3832$8a3a28c0$9eae7a40$@motionview3d.com>
MIME-Version:	1.0
X-IsSubscribed:	yes
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-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id q4MFoNKC029033

> -----Original Message-----
> Sent: Tuesday, May 22, 2012 06:14
> Subject: 1.7.15-1: mintty bash failing to run .NET executables ?
> 
> After that, .NET programs failed to launch at all. The mintty bash
terminal just
> sits there, no CPU or anything else being used, the .NET .exe failing to
launch
> according to Task Manager. (Have left it 10 or 15 minutes to make
> sure.) Ctrl-C / Ctrl-Break, Ctrl-Z fail to have any effect. Clicking the
close 'X' on
> the window housing the mintty terminal just kills it (mintty.exe and
> bash.exe) immediately (as seen in Task Manager) without comment or
> question from Windows.

I had the same problem with 1.7.15, and so did one or two other people.  The
latest developer snapshot fixed the problem for me (so far!).

> roll back your cygwin.dll to 1.7.14-2

I would not suggest doing this.  The last several Cygwin versions had a
series of problems with handling of standard input/output for non-Cygwin
programs; in some situations, the problems were timing-sensitive and did not
occur 100% of the time. 

I would also strongly recommend that you look at setting the new pipe_byte
option in the CYGWIN environment variable (
http://cygwin.com/cygwin-ug-net/using-cygwinenv.html ).  Unfortunately the
documentation has zero indication of why you would need to set this, but to
summarize, you will probably want/need to set this if you are redirecting
standard input to a non-Cygwin program (either .NET or otherwise).

You may find it useful to read some of the archived discussion in the Cygwin
mailing list over the past few months; there are several discussions
regarding these issues that should give you a deeper understanding of the
problems.


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