Many thanks guys - the blocking pipes are being created with PIPE_WAIT and without FILE_FLAG_OVERLAPPED and they successfully block if I build under VC++ but not when I build under Cygwin. I must confess, I don't understand the subtle difference between asynchronous operation and nonblocking operation but I'll see what I can find out from Google.
----- Original Message ----- From: "Christopher Faylor"
Sent: 22 December 2008 17:28 Subject: Re: Named pipes (blocking problem)
If the OP is creating a pipe using CreateNamedPipe and then trying to somehow read it using Cygwin's I/O library then I wouldn't be surprised to see strange behavior. Otherwise, Cygwin does not impose any strange limitations on CreateNamedPipe.
Thanks Christopher. This is really at the heart of what I'm trying to find out. Does Cygwin implement its own versions of CreateNamedPipe() and ReadFile() or does it simply link to the standard Windows versions? If it passes the calls over to Windows then I'm baffled about why I'm observing different behaviour. John -- 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/
