|
From: | address@hidden |
Subject: | [lwip-users] lwip_recvfrom - EWOULDBLOCK error |
Date: | Wed, 3 Oct 2018 10:42:18 +0200 (CEST) |
Dear all,
I have some difficult in the use of lwip_recvfrom function.
I have been using the LwIP 1.4.1 for several years and it works great.
I recently replaced the version 1.4.1 with the 2.0.3 and
encountered some difficults with the lwip_recvfrom function. In the version 1.4.1,
when the connection isn’t blocking and there is no data available then an
EWOULDBLOCK error is set for that socket (sock_set_errno). Instead, in the
version 2.0.3, in the same conditions, an EWOULDBLOCK error is set for errno
variable (set_errno).
According the bug #49848 and task #14275, this change seems to depend on Open Group Standard.
My project is based on a RTOS with several tasks and each of them manages a
socket. Because the errno is a global variable, the errno contains the last
error reported by a socket, so the error contained in the errno could be
overwritten in the instance of checking the errno.
A this point my question is if there is a method for associate the EWOULDBLOCK error to a specific socket. In this way I could check the error later on compared to the occurrence of the error and I’m sure that error is associated to that socket.
Thanks in advance for any support or advice.
Regards
[Prev in Thread] | Current Thread | [Next in Thread] |