[En-Nut-Discussion] Http server

Brett Abbott Brett.Abbott at digital-telemetry.com
Thu Feb 19 20:23:49 CET 2004


Cosmin

A couple of ideas...

1.  Have you tried a second ethernut (just in case).
2. If you have a JTAG unit, trace the location of the heap that is being 
corrupted - this assumes it reproduces in the same place each time (but 
can often be engineered this way), place a breakpoint on the data memory 
at the expected location.  Obviously you will see the owner updating the 
memory, but this will also give you a means to identify what else is 
changing the memory.  This requires you to know what a good heap looks 
like so you can spot the difference.  AVR Studio helps by changing the 
colour of recently changed memory values.
3. As a third thought, to be ignored if you are using the sample code 
EXACTLY unchanged, is that it is very easy to reuse the pointer to the 
device, perhaps initialising or opening it twice, or writing (fprintf) 
to a pointer/device that hasnt been opened - this generally has fatal 
consequence matching the symptoms you see.

Hope this helps
Brett

-- 
-----------------------------------------------------------------
Brett Abbott, Managing Director, Digital Telemetry Limited
Email: Brett.Abbott at digital-telemetry.com
PO Box 24 036 Manners Street, Wellington, New Zealand
Phone +64 (4) 5666-860  Mobile +64 (21) 656-144
------------------- Commercial in confidence --------------------





More information about the En-Nut-Discussion mailing list