Hello to everybody,
I am working with the sockets layer on a lwip stack with a port to
Nucleus RTOS. A few days ago I asked a question dealing with the select
function and semaphores. Further investigations have led me to discover
that the select function gives up waiting for the timeval structure when I
use connect previously. This sounds pretty strange, but now I am sure
about that. In the same piece of code I have written a menu with 2
options. In the first one I use select after listen, and it waits the
introduced value (5 seconds), all ok. But when I choose the second option,
another socket is used with connect, and in the next select call I can see
through debugging that no waiting takes place (the same value is used, 5
seconds). Has somebody experienced any similar problem??? Am I making any
obvious mistake???
Thanks a lot for your useful help.
_______________________________________________
lwip-users mailing list
lwip-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/lwip-users