Message-Id:	<199803300906.LAA33014@ieva06.lanet.lv>
From:	"Andris Pavenis" <pavenis AT lanet DOT lv>
To:	mdevan AT iname DOT com, Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Date:	Mon, 30 Mar 1998 12:04:21 +0000
MIME-Version:	1.0
Subject:	Re: "bash"ing "cat"s.
CC:	djgpp AT delorie DOT com
References:	<Pine DOT OSF DOT 3 DOT 95 DOT 980327201633 DOT 15148A-100000 AT md2 DOT vsnl DOT net DOT in>
In-reply-to:	<Pine.SUN.3.91.980329141953.15237J-100000@is>

> Date:          Sun, 29 Mar 1998 14:20:16 +0300 (IDT)
> From:          Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
> Subject:       Re: "bash"ing "cat"s.

> 
> On Fri, 27 Mar 1998, Mahadevan R. wrote:
> 
> >      This is with reference to the recent thread about "cat -", wherein,
> > I gather, it was concluded that this was a problem specific to "cat".
> 
> No, the conclusion was that this is some bug in Bash which is
> triggered by `cat'.  Once triggered, any program which reads from
> stdin will get EOF immediately, as your examples show.
> 

Did some more testing also under DOSEMU for Linux and also under
MS-DOS 6.22. The problem with EOF in stdin does not appear if the
program reading stdin is invoked directly from COMMAND.COM 
but appears if it is invoked from BASH, Norton Commander and from
FAR 1.50 (Win95 only). Tried also to track system calls from 
COMMAND.COM but didn't find anything interesting

Andris 

- Raw text -