|
From: | Wen Xichang |
Subject: | [lwip-devel] [bug #49848] Non-blocking socket emit a sock error while read return EWOULDBLOCK |
Date: | Thu, 15 Dec 2016 15:16:02 +0000 (UTC) |
User-agent: | Mozilla/5.0 (iPhone; CPU iPhone OS 10_1_1 like Mac OS X) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0 Mobile/14B100 Safari/602.1 |
Follow-up Comment #2, bug #49848 (project lwip): that's exactly what i mean. reading nonblocking socket while EWOULDBLOCK occurred shouldn't cause getsockopt(SO_ERROR) to return any error. found this while porting nginx to lwip _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?49848> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |