On 12/6/2020 12:17 PM, Norton Allen wrote:
On 12/5/2020 6:52 PM, Ken Brown wrote:
On 12/4/2020 8:51 AM, Norton Allen wrote:
On 12/3/2020 8:11 PM, Ken Brown wrote:
I'm traveling at the moment and unable to do any testing, but I wonder if
you're bumping into an issue that was just discussed on the
cygwin-developers list:
https://cygwin.com/pipermail/cygwin-developers/2020-December/012015.html
A different workaround is described there.
If it's the same issue, then I don't think it will happen with the new
AF_UNIX implementation. More in a few days.
It does seem related.
A work around that is working for me is to do a blocking connect() and switch
to non-blocking when that completes. In my application, the connect()
generally occurs once at the beginning of a run, so blocking for a few
milliseconds does not impact responsiveness.
For the record, I can confirm that (a) the problem occurs with the current
AF_UNIX implementation and (b) it does not occur with the new implementation
(on the topic/af_unix branch). With both client1 and client2, I see
"connect() apparently succeeded immediately" using the new implementation.
The new implementation is not yet ready for prime time, but with any luck it
might be ready within a few months.
That sounds great, and exactly like the behavior under Linux. I'd certainly be
happy to test the new implementation as it gets closer, and also happy to expand
or improve the test apps to cover a wider range of functionality and/or
usability (e.g. run both client and server via a fork.) Feel free to let me know
what would be particularly useful.
Thanks. I'll take you up on that when the branch is in slightly better shape.
Ken
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple