2017-01-31 20:11 GMT+08:00 Sandra Gilge :
> 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_thr
>Simon wrote
>I'm not sure I get it. You checked that sockets are used from only one thread?
>The thing to check >would be to ensure that *every* core function (not
>sockets) is only called from tcpip_thread and not >from an interrupt. That
>would indeed be useful for debugging. I could imagine
Patrick Klos-2 wrote
> The SNMP response packet really only have one problem that I can see.
> The community string 'public' is being included in the response, but
> it's length field is incorrect (01 instead of 06). That throws off the
> rest of the packet (which seems to parse fine once you f
Sandra Gilge wrote:
> [..]
> For this I added a function sys_get_thread_id [..] 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?
I'm not sure I get it. You
