[lwip-devel] [bug #27871] Calling tcp_abort() in recv callback can lead to accessing unallocated memory

[Simon Goldschmidt]

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
timeout...

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?27871>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/