From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] cygwin 3.3.0-0.2.6c1f49f83fde (TEST)
Date: Sun, 17 Oct 2021 12:19:59 -0400 [thread overview]
Message-ID: <2c263022-b361-f697-ca7b-5caface23872@cornell.edu> (raw)
In-Reply-To: <E0CDBC6F-4F84-495A-BCA4-A7B049BA8928@house.org>
On 10/16/2021 1:42 PM, Chris Roehrig wrote:
>
> On Mon Sep 27 2021, at 7:26 AM, Ken Brown via Cygwin <cygwin@cygwin.com> wrote:
>
>> On 9/26/2021 8:57 PM, Chris Roehrig wrote:
>>> I have installed this (completely this time) and have encountered no issues with it. I'm getting full gigabit speeds with my rsync transfers. Looks great!
>>
>> Thanks for testing.
>
>
> I've encountered a crash that might be related. I had previously been having occasional crashes/hangs of cat.exe over the years, but this is the first time I've ever gotten an error message:
>
> cygwin error: 0 [fifo_reader] cat 11398 C:\cygwin\bin\cat.exe: *** fatal error - Can't add a client handler, Win32 error 123
This isn't a crash in the usual sense. It's the Cygwin fifo code issuing a
fatal error because an attempt to create a new Windows pipe instance failed.
And it's in code that's been around for a while, so it's not related to the new
pipe implementation.
> cat here is reading from a fifo created with mkfifo.
>
> I've only encountered it once (out of daily runs over the last couple weeks) and don't know how to replicate it. Possibly a race? Looks like my script has tried to mitigate this with a sleep 1 between the mkfifo and the fork: cat < $fifo &
The sleep shouldn't be necessary. If it is, there's a bug in the fifo code.
Can you remove the sleep and see what happens? It would be great if that made
it possible to replicate the problem.
Ken
next prev parent reply other threads:[~2021-10-17 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 1:53 Ken Brown via Cygwin-announce
2021-09-27 0:57 ` Chris Roehrig
2021-09-27 14:26 ` Ken Brown
2021-10-16 17:42 ` Chris Roehrig
2021-10-17 16:19 ` Ken Brown [this message]
2021-10-17 20:52 ` cat fifo hang [Re: [ANNOUNCEMENT] cygwin 3.3.0-0.2.6c1f49f83fde (TEST)] Chris Roehrig
2021-10-17 22:15 ` Ken Brown
2021-10-24 21:51 ` Ken Brown
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=2c263022-b361-f697-ca7b-5caface23872@cornell.edu \
--to=kbrown@cornell.edu \
--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).