delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT sources DOT redhat DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT sources DOT redhat DOT com> |
List-Help: | <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT sources DOT redhat DOT com |
Delivered-To: | mailing list cygwin AT sources DOT redhat DOT com |
Date: | 25 Oct 2000 12:29:33 -0400 |
Message-ID: | <20001025162933.5275.qmail@lizard.curl.com> |
From: | Jonathan Kamens <jik AT curl DOT com> |
To: | cygwin AT sources DOT redhat DOT com |
Subject: | TTY signal-handling problem in current snapshot (20001023) |
(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. jik -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |