From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26368 invoked by alias); 22 May 2012 15:50:16 -0000 Received: (qmail 26354 invoked by uid 22791); 22 May 2012 15:50:14 -0000 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 Received: from mout.perfora.net (HELO mout.perfora.net) (74.208.4.195) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 May 2012 15:50:00 +0000 Received: from JamesJPC (75-146-80-177-Chattanooga.hfc.comcastbusiness.net [75.146.80.177]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MbffJ-1SpLZA37Y5-00JF8h; Tue, 22 May 2012 11:49:59 -0400 From: "James Johnston" To: References: In-Reply-To: Subject: RE: 1.7.15-1: mintty bash failing to run .NET executables ? Date: Tue, 22 May 2012 15:50:00 -0000 Message-ID: <007a01cd3832$8a3a28c0$9eae7a40$@motionview3d.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-05/txt/msg00480.txt.bz2 > -----Original Message----- > Sent: Tuesday, May 22, 2012 06:14 > Subject: 1.7.15-1: mintty bash failing to run .NET executables ? >=20 > 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=A0(as seen in Task Manager)=A0without 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.=20 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