[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #51789] TCP_EVENT_CLOSE, tcp_close() and possible use

From: Simon Goldschmidt
Subject: [lwip-devel] [bug #51789] TCP_EVENT_CLOSE, tcp_close() and possible use of pcb with tcp_output()
Date: Tue, 22 Aug 2017 15:32:44 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Follow-up Comment #3, bug #51789 (project lwip):

Right, I see now how tcp_close() gets called with recv==NULL.

> Further, tcp_close(pcb) will free the pcb if the pcb state is SYN_SENT

OK, if you tell me where a pcb in SYN_SENT accepts a FIN, I'll continue to
investigate this. Until then, I suspect this report is from reading the code.
Please correct me if you actually see a pcb freed by tcp_close() used in


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]