No, same thread. I just meant that I'm calling the netconn functions from a separate thread from the lwip thread. So I should not have mentioned that. However, the symptoms I am having do seem to be as if the conn structure is being written to by another thread. I just don't see it. I only have the one thread accessing the netconn functions. If no one else has reported such behaviour it must be my code. I'm stumped but I'll keep digging. I need to bring in a stump remover.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kieran Mansley Sent: Wednesday, October 07, 2009 4:09 AM To: Mailing list for lwIP users Subject: Re: [lwip-users] conn->err = ERR_CLSD in api_lib.c On Tue, 2009-10-06 at 17:32 -0400, David Shmelzer wrote: > I'm calling netconn_recv() in a loop in another thread with a zero timeout. > help? Does that mean you're using the same connection from two different threads? That would certainly explain the problem. It's not supported I'm afraid. Kieran _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
