lwip-users
[
Top
][
All Lists
]
Advanced
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
[lwip-users] socket API error values
From
:
Fabian Koch
Subject
:
[lwip-users] socket API error values
Date
:
Thu, 13 Mar 2014 09:31:34 +0100
Hey all,
we just ported from 1.3.2 to 1.4.1 and some of our programs stopped working because the error codes the socket API returns apparently changed.
can someone explain, why ERR_ISCONN is mapped to EALREADY in line 145 of sockets.c?
static
const
int
err_to_errno_table[] = {
0,
/* ERR_OK 0 No error, everything OK. */
ENOMEM,
/* ERR_MEM -1 Out of memory error. */
ENOBUFS,
/* ERR_BUF -2 Buffer error. */
EWOULDBLOCK,
/* ERR_TIMEOUT -3 Timeout */
EHOSTUNREACH,
/* ERR_RTE -4 Routing problem. */
EINPROGRESS,
/* ERR_INPROGRESS -5 Operation in progress */
EINVAL,
/* ERR_VAL -6 Illegal value. */
EWOULDBLOCK,
/* ERR_WOULDBLOCK -7 Operation would block. */
EADDRINUSE,
/* ERR_USE -8 Address in use. */
ERR_ISCONN,
/* ERR_ISCONN -9 Already connected. */ <=== this would be how I'd like it ;o)
ECONNABORTED,
/* ERR_ABRT -10 Connection aborted. */
ECONNRESET,
/* ERR_RST -11 Connection reset. */
ENOTCONN,
/* ERR_CLSD -12 Connection closed. */
ENOTCONN,
/* ERR_CONN -13 Not connected. */
EIO,
/* ERR_ARG -14 Illegal argument. */
-1,
/* ERR_IF -15 Low-level netif error */
};
The interesting part is that EALREADY is not defined in the err.h of LwIP. (In ours it is...)
kind regards,
Fabian
reply via email to
[Prev in Thread]
Current Thread
[
Next in Thread
]
[lwip-users] socket API error values
,
Fabian Koch
<=
Re: [lwip-users] socket API error values
,
Simon Goldschmidt
,
2014/03/13
Re: [lwip-users] socket API error values
,
Fabian Koch
,
2014/03/17
Prev by Date:
[lwip-users] Is netconn_write blocking or not
Next by Date:
Re: [lwip-users] socket API error values
Previous by thread:
[lwip-users] Is netconn_write blocking or not
Next by thread:
Re: [lwip-users] socket API error values
Index(es):
Date
Thread