You can just check the code yourself, but no, sys_check_timeouts() should return asap since it is meant to be called as frequently as possible (afap?) and living in the main loop of many systems. However, from time to time, something needs to be done, like for example resending a TCP segment, so it will do something. It does call a system function you provide, though, to get current time in ms. You should first check for blocking there, and then perhaps try to discover the whole scenario to get a clue on where the dragon is lurking. Did you happen to log the traffic so you can correlate crashes to (for example) retransmissions ? Just rambling.
_______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
