Re: [lwip-devel] application above lwip too low - lwip memp overflow

[Kieran Mansley]

On Thu, 2009-01-15 at 17:56 +0300, Mike Kleshov wrote:
> Presumably, the sockets layer will free some pbufs as soon as you read
> some data from the socket. Where exactly does your application get
> stuck?

This sort of error has, in the past, nearly always been down to a memory
leak that results from something like a list being corrupted when two
threads are active in the core stack.  i.e. a bug in the port, or way
the API is being used.  I'm not sure if that's possible here as I'm not
familiar with the setup.

Kieran