From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10110081506.AA19305@clio.rice.edu>
Subject: Re: Bash read problem
To: acottrel AT ihug DOT com DOT au (Andrew Cottrell)
Date: Mon, 8 Oct 2001 10:06:20 -0500 (CDT)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <004301c14fe7$c4214940$0a02a8c0@acceleron> from "Andrew Cottrell" at Oct 08, 2001 08:30:24 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> If you downlaod the Bash 2.04 source and exe and then run the following
> script you will see some debug output (I left it in and It didn't cause any
> problems with me building the other packages) as indicated below. The "read
> answ" should wait for a CR before continuing, but it does not.
> 
> >>> START <<<<
> #! /bin/sh
> #
> echo Start Test
> read answ
> echo You typed in $answ
> echo End Test
> : End of test
> >>> END <<<<

> I did some more tracing with this issue and traced the failure to
> __libc_termios_read() in tmread.c . In tracing __libc_termios_read()  I
> found it calls __libc_termios_read_cooked_tty(). I have not traced into
> __libc_termios_read_cooked_tty() yet.

> I thought I better test Bash 2.05 and it also fails in the same way.

I see this same behavior when I run the executable under Win 95 or NT,
so it is not specific to Win2K.  Maybe it's something broken in the
termios in the cvs libc build?

I suspect someone in workers can give us a hint of where to look :-)