Hi Simon, I'll recap the setup:
1. Non blocking sockets. 2. poll(thread 1). 3. read/write in 2 different threads, but not in parallel, mutex protected. 4. poll may occur in parallel to read/write. But the original problem, as described, is the matter of tcp stream corruption. I wanted to use full duplex as a possible solution(though I wasn't sure what was wrong in my setup to need it). On Tue, Nov 7, 2017 at 10:13 PM, [email protected] <[email protected]> wrote: > Itzik Levi wrote: > >> Now I cant even reach the corruption issue(not sure if solved or not), as >> I constantly getting another assert after a while : "Assertion >> "sock->fd_used != 0" failed at line 344 in lwip/src/api/sockets.c.". >> > > Could you add a description of the call stack or what your application > does when you get that assert? Nonblocking sockets? Select? Read/write > timeout? > > I'm guessing thats why this feature is in alpha level :) >> > > Well, yes, I guess you're right. There are still commits coming in that > area :-) Nevertheless, we need people to test this to get it stable! > > > Thanks, > Simon > > > _______________________________________________ > lwip-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lwip-users >
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
