Date: Thu, 16 Nov 2006 21:44:42 +0000
Message-ID: <4541211900032DA7@mail-1-uk.mail.tiscali.sys>
From: nwann AT tiscali DOT co DOT uk
Subject: peeknamedpipe stdio error
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-15"
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit

I'm having a problem with a windows utility that I have written. It uses
the windows API function peeknamedpipe, readfile and writefile to connect
to a console program that has been compiled with gcc.
The program reads the stderr, stdout and writes to the stdin using these
functions.
This method worked perfectly well until a more recent version of cygwin.dll
has been installed.
Peeknamedpipe will not return that any data has been written until the buffer
is full, this causes problems with writing to stdin. This happened with stderr
before (which wasn't a problem for my program) but now seems to affect stdout.
Another thing I've noticed is that end of lines are now just linefeeds and
not carriage return followed by linefeeds as before.

I think this problem could possibly be due to with how the program I'm connecting
to has been compiled. Maybe it's not flushing the buffers after writing to
them? Unfortunately the programs are created by an automated UML modelling
tool and so my control over the content is limited.

Any help would be appreciated.


___________________________________________________________

Tiscali Unlimited Broadband with FREE weekend calls only 12.99!
http://www.tiscali.co.uk/products/broadband/


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