Should receive have blocked at all since there is data in the recv_mbox?
Overflowing has no bearing on a thread waiting for data when there is data
already in the mbox.

 

Bill

 

  _____  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Piero 74
Sent: Friday, March 07, 2008 10:02 AM
To: Mailing list for lwIP users
Subject: [lwip-users] recv function BLOCK because recv_mbox is full: can
yougive me a solution?

 

Hi all

this is my new problem:

I have a task which calls lwip_recv with the flag MSG_DONTWAIT. 

I saw a strange situation: my recv_mbox is full, so sys_mbox_trypost return
ERR_MEM, so recv_tcp return ERR_MEM and tcp packet is dropped... but recv
remains BLOCKED! In this situation my code cannot check the problem and
close the socket!

I can set size for recv_mbox using high value, but it's not a solution....
can anyone explain how i can trap this problem?

thanks,
Piero

_______________________________________________
lwip-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lwip-users

Reply via email to