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, 17 Jan 2001 10:01:26 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Ctrl-Z hang Message-ID: <20010117100126.A12915@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from dattorro@ccrma.stanford.edu on Mon, Jan 01, 2001 at 10:13:01PM -0800 On Mon, Jan 01, 2001 at 10:13:01PM -0800, Jon Dattorro wrote: >I notice that cygwin hangs permanently when "man " is >invoked and then Ctrl-z (suspended) after viewing a few pages. This bug >is intermittent. This should be fixed in tonight's snapshot. It was an interesting problem. I didn't see the problem on my normal test machine but it failed repeatedly on my laptop. What was happening was that a CTRL-Z would send a SIGTSTP to less which would dutifully process it. bash would step in and grab the tty back from less and *sometimes* less would still be in the process of reading from the tty. This would generate a SIGTTIN,, which would confuse less and cause a hang. So, cygwin no longer will send itself a SIGTTIN in this scenario. It also no longer queues STOP signals which was another problem. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple