Re: [lwip-users] Failed lwip_getpeername() call appears to prevent future socket calls

[Dirk Ziegelmeier]

One more side effect which will be fixed by task #13922: Remove fatal error handling

err is set to ERR_CONN which is a fatal error. lwip_netconn_do_bind() checks last_err and bails out immediately.

Ciao
Dirk

--
Dirk Ziegelmeier * address@hidden * http://www.ziegelmeier.net

On Fri, Sep 30, 2016 at 10:36 PM, Brian Armstrong <address@hidden> wrote:

Hi,

I'm noticing some possibly unintuitive behavior where calling lwip_getpeername() on a socket that's not connected (silly, for sure, but perhaps still valid) appears to prevent any future socket calls from succeeding. For example, it seems to prevent calls to lwip_bind() or lwip_send().

Is this intentional behavior? I suspect this relates to the check by netconn_bind against last_err and netconn_getaddr calling NETCONN_SET_SAFE_ERR. Alternately, it may be that the error here should not be considered fatal.

Just for comparison, when I run this sequence of calls on my local host against its stack, it seems to work fine -- I am allowed to send after a failed call to getpeername().

Thanks!

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users