I would suppose he is using the lwip socket API via a libcurl calls. Maybe the libcurl expects the socket API is at 100% compatible with BSD sockets. If the libcurl handles non-blocking sockets with a standard way ( send - read how many sent - select loop), it may fail due to lwip does not support this concept(http://savannah.nongnu.org/bugs/?31084). However the error is returned and libcurl should deal with it. It depends on the exact explanation of "I see some corruption when I repeat this operation".
>Is there a good starting point to debug this ? Of course, the lwip have a nice debug capability at defined level. Read wiki http://lwip.wikia.com/wiki/Debugging_lwIP You can use the lwip port for linux too and you will get advantage of debugging on a PC platform with standard tools. Martin On 7 February 2011 10:31, Kieran Mansley <[email protected]> wrote: > On Sun, 2011-02-06 at 21:56 -0800, Prashant R wrote: >> Is there a good starting point to debug this ? > > It's almost certainly a threading problem caused by the way you're > interfacing to lwIP. > > Which lwIP API are you using? Does your application have multiple > threads accessing lwIP? Can you give a code example of: > 1) how your application sends and receives packets > 2) how your driver passes received packets to lwIP for processing? > > Thanks > > 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
