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

Previous Next

Package: emacs;

Reported by: Ken Brown <kbrown <at> cornell.edu>

Date: Wed, 25 May 2016 00:27:02 UTC

Severity: wishlist

Found in version 25.1.50

Done: Ken Brown <kbrown <at> cornell.edu>

Bug is archived. No further changes may be made.

Full log

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

From: Ken Brown <kbrown <at> cornell.edu>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 23615 <at> debbugs.gnu.org
Subject: Re: bug#23615: 25.1.50; Which platforms can safely use
 getsockopt(,,SO_ERROR,,)?
Date: Thu, 2 Jun 2016 13:17:34 -0400

On 6/2/2016 12:00 PM, Paul Eggert wrote:
> On Solaris 10 on a host with only IPv4 configured, socket_test.c fails
> with the diagnostic "Can't start server." 'truss' says connect(3,
> 0x00021EE8, 16, SOV_DEFAULT) failed with errno == EOPNOTSUPP.
>
> On Solaris 11 with both IPv4 and IPv6, the same symptoms except errno ==
> EADDRNOTAVAIL.

Thanks for testing.  This means that my test program is not portable 
enough to answer the question in the subject; the failure occurred 
before the program reached the getsockopt call.  I'll see if I can fix that.

Ken
This bug report was last modified 8 years and 351 days ago.

Previous Next

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