Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Tue, 14 Mar 2000 10:33:13 -0500 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: Yet another hanging issue. Message-ID: <20000314103313.A15910@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: ; from fujieda@jaist.ac.jp on Tue, Mar 14, 2000 at 11:02:37PM +0900 On Tue, Mar 14, 2000 at 11:02:37PM +0900, Kazuhiro Fujieda wrote: >After the following procedure, bash consumes a cpu. >1. start bash in the tty mode. >2. launch `notepad'. >3. type `^Z' >bash can't return to the prompt, and continues to consume a >cpu until it is terminated by compulsion. >The strace log is attached below. Thanks for the strace. I can fix this but the behavior may not be what you expect. Any signal which defaults to stopping or aborting the process will abort the process. Only a cygwin process can be stopped, currently. I'm not sure how to change this... cgf