I would first enable LwIP debugging, that already can give a ton of information including allocations done. Stepping through code with LWiP I would sub-optimal because LWiP also expect some responses within some time and you risk loosing connections and looking at the wrong end because of this.The best way to deal with lwip issues like this is to set up a debugger and step through the code until you find where the allocation fails.
You can turn on
Code:
#define MEM_DEBUG LWIP_DBG_ON
Statistics: Posted by rvt — Sat Apr 13, 2024 10:48 am