Re: [lwip-devel] [bug #23119] After a read with timeout, the socket is unuseable

[Piero 74]

Hi.
I'm using socket too, and i have to use non-blocking calls like you.
I didn't use read with timeout (so, i didn't see the bug... thanks for the report to te lwip community), but i implemented all my application using SELECT, for listener, tcp connections and udp connections. 
It could be a workaraound.

Bye,
Piero

2008/4/30 Robert Reither <address@hidden>:

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 mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-devel