[lwip-devel] [bug #63938] On apprupt tcp interrupten the pcb->next list points to itself

[Maximilian Mayr]

Follow-up Comment #4, bug #63938 (project lwip):

Soory for letting you wait. It took me some time to check how lwip wants me to
implement the LWIP_MARK_TCPIP_THREAD / LWIP_ASSERT_CORE_LOCKED and make it
work. I also went back to D.A.V.E (An IDE that creates low level code for our
arm based CPU XMC4700) and checked all settings but everything is correct.

By implementing the checks i found out that there is an ETH interrupt that is
called. But i changed the application and now everything is called from the
same main loop and is not interrupted by anything.

The problem is nothing changed. (It only got way slower).

The functions that where called from the Ethernet input interrupt where:
pbuf_free, lwip_htons, netif->input(...), pbuf_header, pbuf_alloc.

So i guess these arent the problems ?

the tcp thread mutex locks arent even called.



 


    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/bugs/?63938>

_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/