Re: [lwip-users] ERR_MEM in socket layer lwip_send() on non-blocking

[Simon Goldschmidt]

Fabian Koch wrote:
> we encountered some instances of lwip_send() setting sock->err to ERR_MEM even
> on non-blocking sockets.
> As ERR_MEM is not a fatal error and as there are plenty of if statements 
> checking
> for blocking state and doing something different instead of returning this 
> error,
> I wondered if that is a bug.

Well, I'd rather call it an inconsistency (or yes, call it a bug). I think it's 
still
not finally thought through whether ERR_MEM should be retried or abort a 
non-blocking
call. I'd vote for returnin EWOULDBLOCK though...


Simon