Re: [lwip-users] tcpip thread gets stuck when socket is closed

[Kieran Mansley]

On 15 Sep 2011, at 15:43, Stefan Lankes wrote:

> we use LwIP 1.4.0 as TCP/IP stack for an internal OS project. We have already 
> tested some applications, which used the LwIP's Socket API - they work fine. 
> However, if the applications close the socket, the tcpip thread gets stuck 
> and isn't able to handle incoming messages. To analyze this behavior, we 
> defined the macro LWIP_TCPIP_THREAD_ALIVE to print some messages periodically 
> on the screen. This stops by closing the socket. 
> 
> Do you have any idea, why the Socket API doesn't work correctly?

You've probably violated lwIP's threading constraints and corrupted some 
internal state such that the tcpip thread gets stuck in a loop.  If you can 
describe all the different threads you have and how they interface to lwIP that 
would probably reveal the problem.

Kieran