bug#23615: 25.1.50; Which platforms can safely use getsockopt(,,SO_ERROR,,)?

[Ken Brown]

On 5/28/2016 8:57 AM, Eli Zaretskii wrote:
> > From: Ken Brown <kbrown@cornell.edu>

> > Test program attached.  It simulates the situation of bug 23606 (before
> > the bug was fixed).  Here's what happens on Cygwin:
> >
> > $ gcc -o socket_test socket_test.c
> >
> > $ ./socket_test.exe
> > Server listening on port 50176.
> > Attempting client connection...failure: Connection refused.
>
> With MinGW, I get this instead:
>
>   D:\usr\eli\data>socket_test
>   Server listening on port 2213.
>   Attempting client connection...success.
>
> Do we have to have a failure in this case?  Or is the above a valid
> outcome?

It's a valid outcome.  I think the reason the connection is refused on 
Cygwin (and apparently on RHEL 7.2) is that the first addrinfo structure 
returned by getaddrinfo has an IPv6 address.  There's no reason to 
expect this to happen on all platforms.

> Of course, I needed to hack the code quite a lot to get it compile on
> MS-Windows; the result is attached below.  Maybe I broke the code
> while doing that?

No, you didn't.  I get the same results as before with your version, 
after fixing a couple of typos that don't affect the MinGW build.  (You 
forgot a semicolon at the end of line 41, and you misspelled "strerror" 
in line 126.)

> (I don't think calling 'connect' after 'listen' is supposed to work;
> on Windows it predictably fails with EINVAL, as documented on MSDN.)

I think on Posix systems it fails with EISCONN.  I put the call in 
because it's done in the code in process.c that I was imitating, but 
omitting it as you did is fine also.

Thanks for testing.

Ken