Simon wrote
I'm not sure I get it. You checked that sockets are used from only one thread? The thing
to check >would be to ensure that *every* core function (not sockets) is only called
from tcpip_thread and not >from an interrupt. That would indeed be useful for
debugging. I could imagine adding a macro for this >which whould need to be
implemented by an lwIP port.
I did both. In the core functions I compare the calling thread with the tcpip
thread ID.
In the sockets I store for each socket created with socket or accept the thread that
created the socket and compare it in the other socket functions with the calling thread
ID. So I can be shure that a single socket is not "used" by different threads
(i.e. select in one and send in the other). At least in the past things like that caused
problems.