Hi,
do you
mean you have one thread which is "blocked" on a lwip_read, and another thread
call the lwip_close? Right? What lwIP release do you use?
====================================
Frédéric BERNON
HYMATOM SA
Chef de projet informatique
Microsoft Certified Professional
Tél. : +33 (0)4-67-87-61-10
Fax. : +33 (0)4-67-70-85-44
Email : address@hiddenr
Web Site : http://www.hymatom.fr
====================================
Frédéric BERNON
HYMATOM SA
Chef de projet informatique
Microsoft Certified Professional
Tél. : +33 (0)4-67-87-61-10
Fax. : +33 (0)4-67-70-85-44
Email : address@hiddenr
Web Site : http://www.hymatom.fr
====================================
P
Avant
d'imprimer, penser à l'environnement
-----Message d'origine-----
De : address@hidden [mailto:address@hidden De la part de Steve Waligurski
Envoyé : vendredi 10 août 2007 18:05
À : address@hidden
Objet : [lwip-users] proper way to close a TCP socketHi,What is the proper sequence of calls for a client to close a TCP socket connection using lwIP when connected with either static IP or DHCP. My software is in a constant state of read using lwip_read, it only returns when I get a packet. If I call close in this state, nothing gets transmitted to the server and it hangs on the function call. In DHCP mode, it hangs on the call to dhcp_release. I could always shut down the watchdog timer but would rather doing something a little more graceful.Steve
