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 Date: Wed, 25 Oct 2000 14:31:14 -0400 From: Christopher Faylor To: cygwin AT sources DOT redhat DOT com Subject: Re: TTY signal-handling problem in current snapshot (20001023) Message-ID: <20001025143114.A10812@redhat.com> Reply-To: cygwin AT sources DOT redhat DOT com Mail-Followup-To: cygwin AT sources DOT redhat DOT com References: <20001025162933 DOT 5275 DOT qmail AT lizard DOT curl DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <20001025162933.5275.qmail@lizard.curl.com>; from jik@curl.com on Wed, Oct 25, 2000 at 12:29:33PM -0400 On Wed, Oct 25, 2000 at 12:29:33PM -0400, Jonathan Kamens wrote: >(Please CC me on any replies.) > >I just installed cygwin-inst-20001023 on my machine. I found a bug >with TTY signal-handling which is illustrated by the following script: > >1) In a bash Window, run "sleep 10". >2) Immediately hit ctrl-z. >3) Type "kill %1" to send sleep a kill signal. >4) Type "%1" to bring it to the foreground. > >It'll sit there for a while, not accepting any signals, and then >you'll see this message: > >62264820 [main] sleep 226 sig_send: wait for sig_complete event failed, sig -2, rc 258, Win32 error 0 > >And then it'll exit. Thanks for the report. This was actually broken in 1.1.4, too. I've checked in a fix. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com