public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: SOCK_NONBLOCK not honored
Date: Tue, 06 Nov 2018 09:29:00 -0000	[thread overview]
Message-ID: <937c8ba3-e5ef-92d9-7e7c-0645e01ca073@gmail.com> (raw)
In-Reply-To: <20181105200454.GC18379@calimero.vinschen.de>

Am 05.11.2018 um 21:04 schrieb Corinna Vinschen:
> On Nov  1 20:56, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
>> Hi,
>>
>> Looks like CYGWIN defines but does not honor the SOCK_NONBLOCK flag when used with socket(2).
>>
>> (It also defines SOCK_CLOEXEC but I haven't checked whether it is honored -- full disclosure.)
>>
>> Consider the following code:
>
> Spot on, thanks for the testcase.  Neither SOCK_NONBLOCK, nor
> SOCK_CLOEXEC worked as expected.  What was I thinking at the time...?
>
> I pushed a patch and I'm just uploading new developer snapshots to
> https://cygwin.com/snapshots/ while I'm typing.  Please give them a try.
>
>
> Thanks,
> Corinna
>

It reduces the test failures on libuv from 33 to 8  :-))

Thanks
Marco



---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
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

      reply	other threads:[~2018-11-06  9:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01 20:56 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2018-11-05 20:05 ` Corinna Vinschen
2018-11-06  9:29   ` Marco Atzeri [this message]

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=937c8ba3-e5ef-92d9-7e7c-0645e01ca073@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).