|
From: | Art Heers |
Subject: | [lwip-devel] [bug #51789] TCP_EVENT_CLOSE, tcp_close() and possible use of pcb with tcp_output() |
Date: | Mon, 28 Aug 2017 11:19:31 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36 |
Follow-up Comment #6, bug #51789 (project lwip): > TF_GOT_FIN is set in tcp_receive(), which is not called from tcp_process() if the pcb is in SYN_SENT state. OK, I see, thank you. Yes, I did catch this with my emulator when my call back code called tcp_close() when the pbuf parameter was NULL. But admittedly this was a few months ago and further it was with LwIP version 1.4. And since I changed my call back code to not call tcp_close() I have not seen it since. Maybe I can change the discussion here by asking why call tcp_close() inside the call back function? It looks like the LwIP stack takes care of the closing process without the call back function calling tcp_close(). _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?51789> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |