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 From: "Dave Korn" To: Subject: RE: Thread error using named pipe / FIFO on latest version of cygwin Date: Tue, 7 Jun 2005 18:59:55 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20050607102221.1554.qmail@web26710.mail.ukl.yahoo.com> Message-ID: ----Original Message---- >From: Allan Wilkins >Sent: 07 June 2005 11:22 > I am receiving the following error whilst using a FIFO > on the latest versions of cygwin: > > C:\cygwin\bin\bash.exe (2056): *** WFMO failed > waiting for cygthread '(null)' > > To reproduce the problem: > > Open two cygwin bash shells. In the first enter: > > $ mkfifo TEST > $ echo "Hello World" >TEST > > > In the second enter: > > $ while read line > > do > > echo $line > > done > The following error will then be displayed: > > C:\cygwin\bin\bash.exe (2056): *** WFMO failed > waiting for cygthread '(null)' Fails for me too, although at least that '(null)' is replaced by the somewhat more informative 'read_pipe'. Haven't looked any more closely yet. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/