Re: [lwip-devel] Bad memory ref in tcp_input() after tcp_close()

[address@hidden]

Valery Ushakov wrote:
> [..]
> Arguably, callback must not return ERR_OK in this case, since by
> calling tcp_close() without acknowledging incoming data it effectively
> aborts the connection.
> [..]
> If the close is indeed intended to abort the
> connection, then callback should return ERR_ABRT.

I didn't quite get it, yet, but I think returning ERR_OK after calling 
tcp_close() should always be OK for application code. I don't want to 
force people writing raw api code to have to know too much about TCP...

Could anyone file a bug, please?

Simon