Re: [lwip-devel] lwIP 2.0.2 Crash on tcp_out.c line 1148 (TCP_SEQ_LT) EXC_BAD_ACCESS

[address@hidden]

jah6q wrote:
> Hmm, thanks for looking into this it seems that useg is NULL in this case.
>
> To give a 10,000 ft overview, the order of operations from my unit test are:
>
> socket()
> connect()
> write()
> read()
> close()
>
> Here's the stacktrace at crash:

You sent a stacktrace before and this one seems equal. We now know where 
it fails. The question is why.
I'd say you're violating lwIP's threading requirements and as a result, 
"useg" just gets NULL at some point.

Simon