Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: calypso.arrow: stuart owned process doing -bs Date: Tue, 2 Apr 2002 15:54:59 +0100 (BST) From: Stuart Brady X-X-Sender: stuart AT calypso DOT arrow To: Cygwin Subject: Bash bug? - piped loops using builtin echo and stdout Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Note-from-DJ: This may be spam With bash, is the behaviour of "while( true ); do echo foo; /bin/echo bar; done | cat" defined? Is it reasonable for me to expect to see "foo", "bar", "foo", "bar", and so on? With an interactive bash, this isn't what happens when I actually type the command in (i.e. sourcing or executing a script works fine). It only starts going wrong at around the 12th iteration. I can't see anything in the archives, and STFW didn't help either. Can anyone else reproduce this? I'm using Win2k with Cygwin 1.3.10-1 and bash 2.05a-3. This also occurs on Win98 with the same versions of Cygwin and bash, but does not occur on Red Hat 7.2 with bash 2.05-8, nor does it occur on Red Hat 7.0 with bash 2.04-11. Should I post the output of cygcheck -s -r -v here, since I'm not sure that this is even a bug, and am reluctant to spam people? -- Stuart Brady -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/