Differences between named pipes in Windows and Wine

[Qian Hong]

Hi Ryan,

Thanks for the discussion.

On Tue, Jun 14, 2016 at 9:49 AM, Ryan Prichard <ryan.prichard at gmail.com> wrote:
> 3. With Windows, if the server breaks the pipe by closing its handle, the
> client can finish reading the remaining data in the pipe.  Once the data is
> gone, reading from a broken pipe fails with ERROR_BROKEN_PIPE.  Writing to a
> broken pipe fails with ERROR_NO_DATA.  With Wine, once the server breaks the
> pipe, the client cannot read the remaining data, and I/O on a broken pipe
> fails with ERROR_PIPE_NOT_CONNECTED.  (Exception: ReadFile on a server pipe
> still returns ERROR_BROKEN_PIPE.)

If I understand correctly, there was a similar bug which was
discovered when we test Msys2/Cygwin on Wine and later fixed in Wine
Staging:
https://bugs.wine-staging.com/show_bug.cgi?id=404
https://github.com/wine-compholio/wine-staging/blob/master/patches/kernel32-Named_Pipe/0021-server-Do-not-allow-to-queue-async-operation-for-bro.patch




-- 
Regards,
Qian Hong

-
http://www.winehq.org