Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Fri, 16 Mar 2001 21:17:21 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: known issues with current dll
Message-ID: <20010316211721.A3489@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <5627632543 DOT 20010316225211 AT logos-m DOT ru> <20010316163702 DOT A22471 AT redhat DOT com> <20010316164626 DOT A22656 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <20010316164626.A22656@redhat.com>; from cgf@redhat.com on Fri, Mar 16, 2001 at 04:46:26PM -0500

On Fri, Mar 16, 2001 at 04:46:26PM -0500, Christopher Faylor wrote:
>On Fri, Mar 16, 2001 at 04:37:02PM -0500, Christopher Faylor wrote:
>>On Fri, Mar 16, 2001 at 10:52:11PM +0300, Egor Duda wrote:
>>>  my  recent  tty changes broke ^D (eof) in sh.exe and ^Z (suspend) in
>>>bash.exe.   i've  tracked  them down and now figuring a way to fix it.
>>>i'll post a patch when it's ready. 
>>
>>I do see the CTRL-D problem but CTRL-Z is working ok for me in both
>>CYGWIN=tty and CYGWIN=notty modes.
>>
>>CTRL-Z does not interrupt a running process with CYGWIN=notty but it
>>has never done that.  It only works when a cygwin process is waiting
>>for input.
>>
>>CTRL-Z does interrupt a process at any time when CYGWIN=tty.
>
>Nevermind.  I see now it is broken.  I just fixed this behavior recently,
>fwiw.  It's back to the way that it used to work.

This looked so much like the problem that I'd had before, that I thought I
should take a look at it.

There was a race beteen EOF and signal processing.  When the parent pty
sent a signal, it also essentially sent an EOF.  So, it was a race in
the child as to which was processed.  This may well have been a problem
with my previous code, too.

I checked in a fix.  I hope.

cgf