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
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 th
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:
$ cat bug.c
#include
#include
#include
#include
#include
#include
3 matches
Mail list logo