> On Wed, 2009-04-29 at 10:00 +0800, inner T wrote:
>> Thanks for your reply
>>
>>
>> I have tryed this, but if get passive close when lwip_recv() suspend
>> the Client thread, it did not return zero but keep suspend at
>> sys_arch_mbox_fetch().
>> lwip_recv() can return zero only when the connection is not
>> established.
>
> That is not what is supposed to happen: if you have blocked in lwip_recv
> () and the other end closes the connection lwip_recv() should return
> zero immediately.
>
> Kieran
I traced the code but did not find where the lwip send the message to make lwip_recv() goon,
I set some breakpoint after sys_arch_mbox_fetch() but no one reached.
Can you tell me in the code, where does the lwip send message to lwip_recv()? It may help me
fix this problem.