From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Spurious / persistent "exception" condition in half-closed sockets
Date: Sat, 9 Jul 2022 17:05:50 -0400 [thread overview]
Message-ID: <649314d9-4862-af2d-3717-2809b818a820@cornell.edu> (raw)
In-Reply-To: <DM8PR09MB7095465D639E6A96C5615E84A5859@DM8PR09MB7095.namprd09.prod.outlook.com>
On 7/9/2022 11:37 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> Hi all,
>
> It took me awhile to figure this one out, but I think I have a good test case to
> demonstrate a (rather serious, actually) issue with Cygwin sockets and select/poll.
>
> In short, when a reading end of a socket half closes for write (basically, signaling the
> other end of no more data to expect, resulting in TCP FIN and, subsequently, EOF in the other
> end's read()), if that end keeps reading the still incoming remaining data, it will face with
> a lot of "exception" conditions, which are just spurious.
This was fixed in Cygwin 3.3.0, as the announcement of the latter stated:
https://cygwin.com/pipermail/cygwin-announce/2021-October/010268.html
You stated in a different thread that you have chosen to use an old version of
Cygwin for your everyday work. But you can still run a parallel Cygwin
installation that you keep up to date, so that you can check whether a bug has
been fixed before reporting it.
Ken
next prev parent reply other threads:[~2022-07-09 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 15:37 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-09 21:05 ` Ken Brown [this message]
2022-07-09 23:02 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-11 7:52 ` Corinna Vinschen
2022-07-11 8:16 ` 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=649314d9-4862-af2d-3717-2809b818a820@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).