Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 19 Mar 2004 10:50:51 +0000 (GMT)
From: Mark ONeill <mark DOT oneill AT university-museum DOT oxford DOT ac DOT uk>
To: cygwin AT cygwin DOT com
Subject: Problems with fflush() under Cygwin 1.5.8 ...
Message-ID: <Pine.LNX.4.58.0403191045060.30737@raven.linux.ox.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Hi

I am currently porting process communication middleware (developed under
LINUX) to Cygwin. I have managed to find workarounds for missing (mkfifo
-- are named pipes *ever* going to be available under Cygwin?) but
problems still remain.

Major problem is that fflush() does not appear to flush buffered material
to file reliably (I have tested my code on Darwin, LINUX, OSF1 and SOLARIS
all of which work fine) so I suspect that there *may* be a Cygwin/NewLib
problem here.

FYI my code makes extensive use of signal handlers -- I don't know if this
would cause side effects which could mess up stdio on Cywin ...

Has anyone else had similar problems?


Regards

Mark O'Neill


--
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/