[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #23119] After a read with timeout, the socket is unuse
From: |
Robert Reither |
Subject: |
[lwip-devel] [bug #23119] After a read with timeout, the socket is unuseable |
Date: |
Wed, 30 Apr 2008 13:38:33 +0000 |
User-agent: |
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 2.0.50727) |
URL:
<http://savannah.nongnu.org/bugs/?23119>
Summary: After a read with timeout, the socket is unuseable
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: nathan2225
Submitted on: Mittwoch 30.04.2008 um 13:38
Category: sockets
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release:
_______________________________________________________
Details:
If i read from a socket and got a timeout back
(compiled with LWIP_SO_RCVTIMEO and timeout used)
netconn_recv() sets
conn->err = ERR_TIMEOUT.
>From now on i cannot send over this socket anymore.
If i reset the conn->err to ERR_OK, its possible to send again.
Somehow this error shouldn't be delivered over
conn->err
because it can block the whole socket meanwhile this way, even if i reset the
conn->err after reading the err (and setting errno) in socket.c
Greetings
Robert
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?23119>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #23119] After a read with timeout, the socket is unuseable,
Robert Reither <=