lwip-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #51531] getsockopt/SO_ERROR not returning value stored


From: Simon Goldschmidt
Subject: [lwip-devel] [bug #51531] getsockopt/SO_ERROR not returning value stored in errno
Date: Tue, 25 Jul 2017 14:42:20 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Follow-up Comment #6, bug #51531 (project lwip):

In my opinion, we *had* to remove the SO_ERROR handling to meet the
standards.

Of course it's true that we now require thread-local storage for 'errno'. So
from this point of view, keeping the error per socket is more lightweight.

But then, how lightweight is the socket API at all? Do we need an lwIP-special
way of error handling? Maybe we shouldn't remove LWIP_SOCKET_SET_ERRNO but let
'set_errno()' pass the socket, too. Then, everyone having thread-local storage
problems could store the error like they want, giving up standards
compatibility on their own...?

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?51531>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]