[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #27871] Calling tcp_abort() in recv callback can lead
From: |
Kieran Mansley |
Subject: |
[lwip-devel] [bug #27871] Calling tcp_abort() in recv callback can lead to accessing unallocated memory |
Date: |
Mon, 02 Nov 2009 09:09:00 +0000 |
User-agent: |
Opera/9.80 (X11; Linux i686; U; en) Presto/2.2.15 Version/10.00 |
Follow-up Comment #3, bug #27871 (project lwip):
I don't mind applications using the raw API being able to call tcp_abort() -
the raw API is by design low level, so being able to do things that
applications couldn't normally do is OK. However, documenting cases like this
where it is not possible to use tcp_abort() is probably wise. i.e. I think
this is best solved with documentation rather than changing the code.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?27871>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #27871] Calling tcp_abort() in recv callback can lead to accessing unallocated memory,
Kieran Mansley <=