I´m using LWIP 2.0.0RC2 (but the problem should also be in 1.4.1) with
FreeRTOS and a own developed HTTP server.
A collegue of mine has written a tool to stress test a webserver in the way
that it connects to the webserver and only sends "GET /index.html" and then
immediatly closes the connection
I would start by checking that the ethernet driver works, the port
works, take a known to work application and make sure that everything
works.
If errors arise here, it is quite possible that either the driver is
buggy or the port is buggy. All calls to low-level functions must be in
the same
I finally fixed this problem. I was using a pcb after it was freed (the
error callback freed the pcb) and I also had some synchronity problems.
What I don´t get is, why does the LWIP code not check if the pcb us already
freed? Does it assume it only gets right and working pcbs?
> I would start
You should not free the pcb in the error callback, it does not get a pcb
as a parameter (unless you provide it). It is intended for you to free
your resources (if any).
Some people advocate for the check your goesintos mantra.
I personally prefer smaller and tighter code.
There is a nice compro
