This is the mail archive of the
mailing list for the Cygwin project.
RE: Cygwin passes through null writes to other software when redirecting standard input/output (i.e. piping)
- From: "James Johnston" <JamesJ at motionview3d dot com>
- To: <cygwin at cygwin dot com>
- Date: Wed, 9 May 2012 19:21:34 -0000
- Subject: RE: Cygwin passes through null writes to other software when redirecting standard input/output (i.e. piping)
- References: <email@example.com> <20120427143753.GO25385@calimero.vinschen.de> <firstname.lastname@example.org> <4F9B38FB.email@example.com> <20120428052727.GA23749@ednor.casa.cgf.cx> <4F9BD262.firstname.lastname@example.org> <4FAABEAE.email@example.com>
> -----Original Message-----
> Sent: Wednesday, May 09, 2012 19:00
> Subject: Re: Cygwin passes through null writes to other software when
> redirecting standard input/output (i.e. piping)
> I can't say with 100% certainty, but I would bet with 90+% confidence that
> is a bug in MS's libraries -- they "cheat" and use a null/0 byte read as a
> signal for end of file rather than sending out-of-band information that *nix
>From examining .NET Framework source, it seems clear to me they did not plan on message pipe inputs. Win32 ReadFile API normally uses a zero byte read to indicate end-of-file; I think it's not cheating. Pipes present a special case. I'm not sure how MS's runtime libraries could send out-of-band information; the operating system does not really support this as far as I know?
Of course, these libraries are very widely used...
> Essentially you need a 'shim' layer between a POSIX compliant subsystem
> to NON-POSIX compliant programs.
> I'm sure that in the case that my assumptions are true, you wouldn't want to
> deliberate put something in cygwin that would make it less POSIX compliant
> it is only to support external-to-cygwin, NON-POSIX compliant programs...
> Note -- I use programs between cygwin and Windows 'alot', so I want these
> to work as well.
Maybe I'm naÃve and this is harder than it looks, but couldn't Cygwin determine if the program being piped to links with CYGWIN1.DLL (or similar detection technique), and then use byte or message pipes accordingly? Example:
# Byte pipe used because Win32Program.exe does not link with CYGWIN1.DLLL
cat Testfile.txt | ./Win32Program.exe
# Message pipe used because grep links with CYGWIN1.DLL
cat Testfile.txt | grep Hello
# Message pipe still used because the program we are calling links with CYGWIN1.DLL
./Win32Program.exe | grep Hello
If that is still not POSIX compliant enough for the sending program (e.g. "cat" in this example), then I suppose Cygwin could automatically insert a message-to-byte pipe shim like the author proposes. That seems pretty kludgy though.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple