[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] LWIP Threading and other issues

From: Axel Lin
Subject: Re: [lwip-users] LWIP Threading and other issues
Date: Thu, 2 Feb 2017 11:15:51 +0800

2017-01-31 20:11 GMT+08:00 Sandra Gilge <address@hidden>:
> Hallo,
> since I have some problems with ASSERTS where it was suspected these are
> threading issues I added some debug code which check if tcpip functions are
> called from another thread than the tcpip thread.
> For this I added a function sys_get_thread_id in sys_arch.h and a global
> variable that stores th the thread ID of the TCPIP thread on startup.
> Also I added a check in sockets.h. I added the element threadId in struct
> lwip_sock and set it with the ID of the calling thread in alloc_socket. Then
> I compare in get_socket the ID in lwip_sock with the calling thread and the
> tcpip thread.
> This could be a useful debug feature for all LWIP users to be added in the
> LWIP Stack?
> Still (without any threading issues) I have following two problems with the
> stack:
> 1. unsent oversize mismatch
> When stressing my system with a flood of HTTP get requests getting JPEG
> images, I get (very sporadically) the assert "unsent_oversize mismatch (pcb
> vs. last_unsent)"
> TCP_OVERSIZE was set to TCP_MSS. I set TCP_OVERSIZE to 0 now, so this can't
> happen any more. But still I'm a little bit concerned about that.

Hi Sandra,
Which LwIP version are your testing? The git tree/v2.0.x/ or v1.4.x?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]