[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #28968] some request & DNS bug
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #28968] some request & DNS bug |
Date: |
Mon, 22 Feb 2010 08:45:53 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2) Gecko/20100115 Firefox/3.6 |
Update of bug #28968 (project lwip):
Status: None => Fixed
Assigned to: None => goldsimon
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
Fixed the dns bug, thanks for reporting. That's the problem with having too
many configuration options: you always risk not compiling parts of the stack
after making changes...
I'm not convinced about the socket return value though: As I read it,
ETIMEOUT is a timeout that is returned when
a) connect() fails (no response after x retransmissions) or
b) send() times out
In both cases, the connection is dead afterwards.
Since we only use ERR_TIMEOUT with LWIP_SO_RCVTIMEO when accept() or recv()
times out, EWOULDBLOCK seems like the better error to me (although the
specification doesn't mention which is the correct value since it doesn't
mention recv- or accept-timeout).
PS: The summary is not very informative :-)
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?28968>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/