|Subject:||Re: [lwip-users] lwip with libcurl and memory corruption !|
|Date:||Mon, 7 Feb 2011 08:54:52 -0800|
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".
Of course, the lwip have a nice debug capability at defined level.
>Is there a good starting point to debug this ?
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.
On 7 February 2011 10:31, Kieran Mansley <address@hidden> 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?
> lwip-users mailing list
lwip-users mailing list
|[Prev in Thread]||Current Thread||[Next in Thread]|