Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 29 May 2003 05:04:26 -0700
From: Dario Alcocer <alcocer AT helixdigital DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: problem suspending "man bash" (intermittent)
Message-ID: <20030529050426.A4311@ns.helixdigital.com>
References: <Pine DOT LNX DOT 4 DOT 44 DOT 0305281034161 DOT 2090-200000 AT ajax DOT its DOT yale DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.LNX.4.44.0305281034161.2090-200000@ajax.its.yale.edu>; from lev.bishop@yale.edu on Wed, May 28, 2003 at 11:13:41AM -0400

On Wed, May 28, 2003 at 11:13:41AM -0400, Lev Bishop wrote:
> Windows XP home edition
> GNU bash, version 2.05b.0(9)-release (i686-pc-cygwin)
> cygwin dll version 1.3.22
> cygcheck -s -v -r attached
> 
> So I have observed a strange phenomenon, where if I execute "man bash" in
> (using bash) and then suspend with ^Z, maybe one time in 4 there
> is a situation where the first keypress after the suspend still somehow
> gets sent to less rather than to the shell. Subsequently the shell works
> fine but when I "fg man" it only wants to draw the display a line at a
> time (ie it never refreshes the screen, even with ^L). Strangely, this
> behaviour happens much more frequently for "man bash" from xterm and not
> from the console, and even more strangely it seems much more likely to
> happen with the bash man page instead of others, though I have
> occasionally seen it with, eg, "man man".  If you're looking to reproduce
> it, for me the best way is "man bash" from an xterm then repeatedly ^Z and
> "fg" until this happens (usually after 4 or 5 tries).

I tried reproducing this, but I don't get the same exact results. For
me, it takes 7 or 8 tries, and all I get is a missing '[1]+ Stopped'
message from bash; the next keystrokes still go to bash, though. The
problem seems to go away if I use 'fg' instead of 'fg man'. I was not
able to

It looks like some sort of race condition in the signal handling, but I
couldn't tell you where (cygwin, bash, less) it is. If you have access
to a Unix machine, it might be interesting to see if you can reproduce
this. Who knows, it might turn out to be a bash bug.

-- 
Dario Alcocer -- Sr. Software Developer, Helix Digital Inc.
alcocer AT helixdigital DOT com -- http://www.helixdigital.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/