GNU bug report logs - #23615
25.1.50; Which platforms can safely use getsockopt(,,SO_ERROR,,)?

Previous Next

Full log

Message #20 received at 23615 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ken Brown <kbrown <at> cornell.edu>
Cc: 23615 <at> debbugs.gnu.org
Subject: Re: bug#23615: 25.1.50; Which platforms can safely use
 getsockopt(,,SO_ERROR,,)?
Date: Sat, 28 May 2016 20:48:45 +0300

> Cc: 23615 <at> debbugs.gnu.org
> From: Ken Brown <kbrown <at> cornell.edu>
> Date: Sat, 28 May 2016 13:18:27 -0400
> 
> > 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.

OK, thanks.  So hopefully others will chime in with results from other
platforms.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.