On Wed, 2009-07-22 at 05:30 -0700, Chris_S wrote: > I know this isn't a lot to go on, but I suspect it must be exhausting some > resource. Just not sure which one. I'm looking for ideas on what > variables/resources to watch that could be causing this kind of problem.
If you can get at some debug output, turn on the LWIP_DEBUG code and see if that throws anything up. Also turn on the LWIP_STATS code and arrange for something to dump the statistics counts - this should show if any of the memory or connection resources are running out. Kieran _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
