AW: [En-Nut-Discussion] What stops a Nut...

[Ernst Stippl]

Hi Don!

One thing I found useful was to have thread looping doing printf (" avail:
%x\n",  NutHeapAvailable ()); every 30 seconds (or whatever the right timing
will be for you) this helped me narrowing down a mem leak which brought my
system to an unexpected stop sometimes ....

regard
ernst 

-----Ursprüngliche Nachricht-----
Von: en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de] Im Auftrag von Don Ingram
Gesendet: Montag, 24. Juli 2006 04:30
An: Ethernut User Chat (English)
Betreff: [En-Nut-Discussion] What stops a Nut...

Hi all,

I am in the ongoing process of investigating an intermittent failure of a
protocol conversion application running on an AVR based unit & am looking
for suggestions on areas to instrument.

Currently I am generating a set of tools for looking a trends in memory
usage ( heap & thread stack ),async interrupt rates, task cycle times &
states.  Henrik has suggested an interesting issue which may result from
incorrectly set priority levels locking out certain tasks under high load
from the network.

The idea is to generate a histogram for each of these areas & hourly write
the data set to EEPROM.  As the current issue presents about every 10 hours
or so about 24 hrs of data storage should be fine.

Any ideas on other areas that I should be monitoring?


--
Cheers

Don
_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion



--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.4/396 - Release Date: 24.07.2006



-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.4/396 - Release Date: 24.07.2006