I'm not well versed in sockets here, but since you are using sockets, there shouldn't be application-related pbuf free issues if threading rules are respected. Somewhere in your vendor provided code, someone did not play by the rules. You have an OS, you have a port, you have a driver, you have many places to search. You should check for modified code, and threading misuse, that is, all code for one socket goes in one thread, all low-level code goes in one thread. I would probably start by tracing the free operation to its caller and wondering why is it trying to free it or why it has been freed before, and by whom. Most of the times, when it is not a threading issue, it is a driver issue.
_______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
