Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Thu, 24 Jun 1999 15:12:39 -0400
From: Chris Faylor <cygwin AT sourceware DOT cygnus DOT com>
To: John Wiersba <John DOT Wiersba AT medstat DOT com>
Cc: cygwin users <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: cat broken
Message-ID: <19990624151239.F2783@cygnus.com>
References: <03F4742D8225D21191EF00805FE62B990205E17F AT AA-MSG-01>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <03F4742D8225D21191EF00805FE62B990205E17F@AA-MSG-01>; from John Wiersba on Thu, Jun 24, 1999 at 03:02:58PM -0400

On Thu, Jun 24, 1999 at 03:02:58PM -0400, John Wiersba wrote:
>OK, then it appears that every snapshot since 5/24 has this bug in it.  I'm
>not exactly sure why it is showing up so frequently in my environment.  I
>saw this virtually every time when piping
>   ls | grep | perl

You've actually tried every snapshot from 5/24 and 6/15?  Wow.  I can't
duplicate this problem, FWIW.  It works fine for me.

>Could these two bugs be related?  It seems that when the terminal emulation
>bug went away, simultaneously the fhandler_base::fork_fixup bug appeared.

Probably not.

-chris

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com