Hey all,
our sys_arch layer is very conservative at the moment. It basically makes
Assertions at any given wrong turn.
Also when someone is waiting for sys_arch_mbox_fetch to finish (e.g.
netconn_accept()), and the mbox is deleted, it fires an Assertion.
This happens now when I want to netconn_c
On Thu, 2009-10-15 at 16:17 +0200, Fabian Koch wrote:
>
> Hey all,
>
> our sys_arch layer is very conservative at the moment. It basically
> makes Assertions at any given wrong turn.
> Also when someone is waiting for sys_arch_mbox_fetch to finish (e.g.
> netconn_accept()), and the mbox is dele
Your conservative approach is the right thing to do since basically,
what you are trying to do is not supported! Calling netconn_close()
while the connection waits in netconn_accept() means you are using one
netconn from two different threads, which is not supported.
Simon
Fabian Koch wrote:
I did a wireshark capture and the window size from lwip keeps decreasing
by the packet length received by lwip for each transaction. When it
finally decreases to less than the packet size my s/w hiccups because it
expects a full packet. So this problem exposed a flaw in my software. Is
anyone else
