Hi Kieran, Thanks for your reply. The boys at TI figured out my problem for me.
If anyone is interested in my solution here is the limk to the forum thread. http://www.luminarymicro.com/component/option,com_joomlaboard/Itemid,92/func,view/id,6658/catid,5/ Thanks again. Mat On Thu, Sep 3, 2009 at 5:34 AM, Kieran Mansley <[email protected]> wrote: > On Fri, 2009-08-28 at 19:50 -0700, schneiderham wrote: > > > Although I am happy to just build with MEMP_SANITY_CHECK I am sure this > is a > > band-aid. Does anyone have any ideas why this could fix my memory leak? > > It can't be a real fix. It's hard for anyone else to debug this sort of > thing as we don't have access to the system that is causing the > problems. I can only suggest adding more assertions and debug code to > verify that memory is freed properly. Could you, for example, scribble > a known sequence to memory when you free it, and then once the leak has > occurred dump all your memory and work out which bits have not been > freed correctly, and work back from there to see where they came from? > Could you use the lwIP stats (perhaps with some additions) to track down > which type of memory is being leaked? > > The fact that the leak depends on the packet rate is very odd, and > doesn't bode well for a simple solution! > > Kieran > > > > _______________________________________________ > lwip-users mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/lwip-users > -- Regards, Mathieu Schneider Firmware Developer ______________________________________________________ Pacific Design Engineering, 8505 Eastlake Drive, Burnaby, BC, CANADA, V5A 4T7 Phone: 1 (604) 421-1311 Ext: 39 Toll free: 1 (800) 561-3322 Fax: 1 (604) 421-9202 ______________________________________________________
_______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
