[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #52113] recv callback: To free or not to free pbuf whe
|
From: |
Simon Goldschmidt |
|
Subject: |
[lwip-devel] [bug #52113] recv callback: To free or not to free pbuf when returning ERR_ABRT? |
|
Date: |
Mon, 25 Sep 2017 15:46:22 -0400 (EDT) |
|
User-agent: |
Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 |
Follow-up Comment #1, bug #52113 (project lwip):
This is indeed unclear. I guess noone ever really thought about this
unclarity. However, given the applications around, I guess your solution is
correct: most applications returning ERR_ABRT will call tcp_close() after
evaluating the pbuf and then fall back to aborting, eventually. (I'm not sure
if this is really needed any more though)
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?52113>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/