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 compromise in the form of assertions that can be easily
disabled once code has been (kind of) debugged, and lwIP more or less
follows this approach.
If you could give more details on the exact sequence you called
functions and/or the code followed, perhaps one of the developers
"fixes" this one you've found and an assertion is triggered next time.
Or did you disable assertions ?
_______________________________________________
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
