Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <4.3.2.7.2.20011011094427.00b7bc60@san-francisco.beasys.com> X-Sender: andyp AT san-francisco DOT beasys DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 11 Oct 2001 09:46:27 -0700 To: Charles Wilson From: Andy Piper Subject: Re: More problems with subprocesses in 1.3.3 Cc: cygwin AT cygwin DOT com In-Reply-To: <3BC52920.90905@ece.gatech.edu> References: <4 DOT 3 DOT 2 DOT 7 DOT 2 DOT 20011009125357 DOT 00b61b50 AT san-francisco DOT beasys DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed At 01:07 AM 10/11/01 -0400, Charles Wilson wrote: >>There seems to be a regression in cygwin 1.3.3 with subprocess handling. >>I have raised the issue before where it is impossible to ^C a subprocess >>that is running inside of a shell script with CYGWIN=tty. For instance >>running a shell script that runs java. However, the saving grace used to >>be that you could ^Z the script and then do kill %1 and that would kill >>off the shell *and* subprocess. Now even this doesn't work, if you do ^Z >>and kill %1 the shell script dies but the underlying process doesn't. > >Andy - can you try a snapshot of the cygwin dll? There have been a lot of >changes in the process handling code between 1.3.3 and pre1.3.4. Sure, although I am a little wary. Since I started using 1.3.3 I have also seen my entire machine lock-up (NT 4.0) a couple of times. When this happens my productivity goes through the floor so I backed up to 1.3.2 and haven't had any more lockups. andy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/