[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #27871] Calling tcp_abort() in recv callback can lead
[lwip-devel] [bug #27871] Calling tcp_abort() in recv callback can lead to accessing unallocated memory
Fri, 20 Nov 2009 17:54:44 +0000
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:220.127.116.11) Gecko/20091102 Firefox/3.5.5
Follow-up Comment #4, bug #27871 (project lwip):
> I think this is best solved with documentation rather than
> changing the code.
I don't know about that: tcp_abort is explicitly mentioned in rawapi.txt, so
it might be used in some applications for a while now.
I don't think a 'small' change in that doc file will draw much attention and
thus this might be a bug in many applications.
After all, from where should a raw-api application call tcp_abort() if not
from one of the pcb callbacks? The only place would be a self-created
Reply to this item at:
Nachricht geschickt von/durch Savannah