delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RCVD_IN_SORBS_WEB,SPF_HELO_PASS,TW_RX |
X-Spam-Check-By: | sourceware.org |
From: | "James Johnston" <JamesJ AT motionview3d DOT com> |
To: | <cygwin AT cygwin DOT com> |
References: | <CA+7con=b9M5a_zuvg97L0wcdTVfLG=Ye8+0CPdPdgTNKn5JEtA AT mail DOT gmail DOT com> <05f101cd32bf$d16a9d60$743fd820$@motionview3d.com> |
In-Reply-To: | <05f101cd32bf$d16a9d60$743fd820$@motionview3d.com> |
Subject: | RE: rxvt loses output connection with non cygwin console processes |
Date: | Tue, 15 May 2012 17:30:34 -0000 |
Message-ID: | <05f201cd32c0$706ec670$514c5350$@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 |
I apologize, I forgot to mention that I tried both with and without the new "pipe_byte" CYGWIN option. It made no difference. To OP: you'll definitely want to look into using the new "pipe_byte" option since you are working with non-Cygwin processes. See the thread I started late last month titled "Cygwin passes through null writes to other software when redirecting standard input/output". If you redirect standard input for a non-Cygwin program, you'll be affected. > As the OP notes, I also only have this problem when running the test > program from a "GUI" terminal. It seems that any program doing a null write > to standard output (and probably standard error?) will trigger the problem. > > From Windows command prompt / standard Windows console window: > Running Cygwin.bat to start Cygwin and then running ./Test.exe works fine. > > From mintty.exe: Running ./Test.exe causes bash to hang. Test.exe runs to > completion and terminates, but bash doesn't get the hint. CPU usage is at > 0%. If I use Windows Task Manager to kill bash.exe, then mintty.exe > correctly terminates. > > From rxvt.exe: Running ./Test.exe causes bash to hang like with mintty. > Test.exe runs to completion and terminates but bash is hung. For some > reason, a thread in rxvt spins in an infinite loop, sucking 100% of a single CPU > core. The hung bash.exe doesn't use any CPU. If I use Windows Task > Manager to kill bash.exe, then rxvt.exe correctly exits its loop and > terminates. -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |