[lwip-devel] [task #14275] sockets should only keep asynchronous errors for sock->err

[Simon Goldschmidt]

Follow-up Comment #1, task #14275 (project lwip):

2.10.10 Pending Error

Errors may occur asynchronously, and be reported to the socket in response to
input from the network protocol. The socket stores the pending error to be
reported to a user of the socket at the next opportunity. The error is
returned in response to a subsequent send(), recv(), or getsockopt() operation
on the socket, and the pending error is then cleared.

2.10.15 Asynchronous Errors

If any of the following conditions occur asynchronously for a socket, the
corresponding value listed below shall become the pending error for the
socket:

ECONNABORTED, ECONNREFUSED, ECONNRESET, EHOSTDOWN, EHOSTUNREACH, EMSGSIZE,
ENETDOWN, ENETRESET, ENETUNREACH

2.10.16 Use of Options

The SO_ERROR option is used only on getsockopt(). When this option is
specified, getsockopt() shall return any pending error on the socket and clear
the error status. It shall return a value of 0 if there is no pending error.
SO_ERROR may be used to check for asynchronous errors on connected
connectionless-mode sockets or for other types of asynchronous errors.
SO_ERROR has no default value.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?14275>

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