Hi ,
So I am getting the data as expected , however I have replaced socket calls
in libcurl with lwip_ calls .
Yes Martin in right in the sense that libcurl is doing the the send -read -
select loop .
Thanks ,
On Mon, Feb 7, 2011 at 1:47 AM, Martin Velek wrote:
> I would suppose he is usin
I am currently running this on an embedded platform .
I am able to successfully send and receive HTTP using lwip however I see
some corruption when I repeat this operation .
This consistently happens after around 4 iterations of this use case .
I am looking for clues to debug this . For libcu
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
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
