From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Pipes Again -- a simple test case
Date: Fri, 08 Jan 2016 16:29:00 -0000 [thread overview]
Message-ID: <83235106e7ed2fcfde26293d156be51d@xs4all.nl> (raw)
In-Reply-To: <20160108151933.GI20447@calimero.vinschen.de>
On 2016-01-08 16:19, Corinna Vinschen wrote:
> On Jan 4 10:24, Houder wrote:
>> On 2016-01-04 09:52, Marco Atzeri wrote:
>> >On 04/01/2016 09:03, Houder wrote:
>> >>Hi Corinna,
>> >>
>> >>I have been looking for an STC to show why cmp fails on Cygwin (and to
>> >>show the
>> >>difference between Cygwin and Linux).
>> >>
>> >>The STC below creates a pipe (pipe() is used), followed by calls to
>> >>fstat() and
>> >>stat() for both the read end and the write end of the pipe.
>> >>
>> >>(I also tested with popen()/pclose(): same result)
>> >>
>> >>Regards,
>> >>Henri
>
> Thanks for the STC. However, given how this stuff works internally,
> I have no good solution off the top of my head. I played with various
> ideas but to no avail. I add this to my TODO list, but I probably
> won't have a quick solution :(
>
>
> Thanks,
> Corinna
>
>
> P.S: It would be really helpful if you could stick to the original
> thread and simply use "reply-to" once a discussion has started.
> It's very confusing having to connect the various threads.
> Thanks.
Perhaps David B. can be helped by a Cygwin-specific patching to "cmp"?
Eric?
... replacing the call to fstat() by a call to stat() ...
(as shown in https://cygwin.com/ml/cygwin/2015-12/msg00348.html)
By the way, thank you for reporting back to "us" about this. I already
feared that a "general" solution would have to wait ... You have already
too much on your plate.
As a final point, I also tested FIFOs and (unix domain) sockets.
FIFOs pass the test, sockets do not.
Regards,
Henri
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-01-08 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 8:03 Houder
2016-01-04 8:52 ` Marco Atzeri
2016-01-04 9:24 ` Houder
2016-01-08 16:13 ` Corinna Vinschen
2016-01-08 16:29 ` Houder [this message]
2016-01-08 18:44 ` Corinna Vinschen
2016-01-11 15:40 ` Corinna Vinschen
2016-01-11 15:47 ` Henri
2016-01-11 16:20 ` Corinna Vinschen
2016-01-11 16:25 ` Henri
2016-01-11 19:48 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83235106e7ed2fcfde26293d156be51d@xs4all.nl \
--to=houder@xs4all.nl \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).