[lwip-devel] [bug #20147] getsockopt() with SO_ERROR option

[Frédéric Bernon]

Follow-up Comment #2, bug #20147 (project lwip):

(please, answer by the bug tracker to get a trace)

>Yup, the fix works good with a small correction.
>sock_set_errno(sock, err_to_errno(sock->conn->err)); /* PATCH
>note: sock->conn->err instead of conn->err*/

Yes you're right. Can you also confirm that err_tcp is called?


>But the returned socket error is EIO (0x5) which seems to be inconsistent
with the error values returned by the standard getsockopt() error values. I
guess we have to return EINVAL if connection is closed.
>http://compute.cnr.berkeley.edu/cgi-bin/man-cgi?getsockopt+3

There is a table to match lwip error code with BSD error code (at the
beginning of sockets.c file). In this table, you could see:

EIO,           /* ERR_ARG     -8      Illegal argument.        */

Perhaps, if you display the "err" field in err_tcp(), perhaps the code is
ERR_ARG. One other possibility is that the "err" code is not "inside" the
err_to_errno_table (in such case, EIO seems to be the value). Can you display
err from err_tcp, and sock->conn->err, and tell me your values?



    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via/par Savannah
  http://savannah.nongnu.org/