From: Ken Brown <kbrown@cornell.edu>
To: "Morten Kjærulff" <mortenkjarulff@gmail.com>, cygwin@cygwin.com
Subject: Re: name pipe problem: 1 writer, multiple concurrent readers
Date: Fri, 3 Jul 2020 07:09:43 -0400 [thread overview]
Message-ID: <e3077fac-26a6-fca2-3c3a-53a47a947b9c@cornell.edu> (raw)
In-Reply-To: <CA+7cx1o2huaWH6s4cuwzyYQVuFgAJNBsi_bVWDdCzn-W-EAhUQ@mail.gmail.com>
On 7/2/2020 1:50 PM, Morten Kjærulff via Cygwin wrote:
> I think we got a new release around the beginning of June, right?
> You said that there were still issues (I can confirm).
> If it can help, here is the output I see today of above scripts:
>
> $ ./tp.sh
[...]
> 0 [fifo_reader] diff 1806 C:\cygwin\bin\diff.exe: *** fatal
> error - Can't update my handlers, Win32 error 87
Thanks for the report and the simple test case. Obviously I still have more
work to do on this.
Ken
next prev parent reply other threads:[~2020-07-03 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 11:26 Morten Kjærulff
2020-05-19 13:14 ` Ken Brown
[not found] ` <CA+7cx1pjvJOzMM3bwspdWGHowC+dSkPx+SrOH6wtyRO367hCJQ@mail.gmail.com>
2020-05-20 22:03 ` Ken Brown
2020-07-02 17:50 ` Morten Kjærulff
2020-07-03 11:09 ` Ken Brown [this message]
2020-07-16 19:26 ` Ken Brown
2020-08-07 8:06 ` Morten Kjærulff
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=e3077fac-26a6-fca2-3c3a-53a47a947b9c@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
--cc=mortenkjarulff@gmail.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).