Re: [lwip-users] how to debug MEMP_OVERFLOW_CHECK

[Liam Staskawicz]

Fortunately, it turns out that I simply had an error in my build setup and all 
is well with lwIP.  It's all working as advertised - thanks very much, and 
sorry for the noise.

Liam

On Apr 12, 2010, at 3:20 AM, Simon Goldschmidt wrote:

> 
> Liam Staskawicz wrote:
>> Hi - I'm using the 1.3.2 sockets api, and am binding and then listening on
>> a port, then accepting new TCP connections, writing a short message to
>> them and closing them in a loop.  This works OK for a few (4) connections, 
>> and
>> then I was starting to see some failures.  I turned on
>> MEMP_OVERFLOW_CHECK, set at 2, and it's catching some overflows.
>> 
>> Is there a common cause of this kind of problem?
> 
> Not really. It depends on which pool had an overflow. If you can break into 
> the debugger when it happens, try to find out for which pool 
> memp_overflow_check_element() is called. I'll try to improve the debug 
> output, but that might take some time.
> 
> Simon
> -- 
> GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
> 
> 
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users