AVR-Chat

>
> > Usage of ram, and register variables would be interesting.
> > IE who mucks with Thingy_pointer or  Other_thingy appears unused..
>Not sure exactly what you mean here, all refs to a variable can be
>displayed, and the symbol table display shows unreferenced symbols.

A very common problem is where one routine messes with another's variables.
Either by direct reference, or indexed as My_Ram+5 accidentally stepping on 
Your_Ram


>* Detection of unused operation results (eg. alter a variable, then
>without using the new value, alter it again).

Good

>* Calculation of maximum stack depth to detect collision with variable 
>storage.

Maybe thorny, but good idea.


>* Calculation of path lengths to come up with maximum execution and
>interrupt service times.
>and probably many more...

This is not brilliant, only tedoius, but it's still quite a useful thing.
Many times the tedious steps are the ones that don't get done, and 
computers are good at tedious.

> > I wrote one application where I deliberately overlapped my input buffer,
> > output buffer, and stack space in SRAM, but with careful design, it was 
> fine.
>*Very* careful I imagine. I'd just use the next chip up, with more RAM

What 8 pin chip, has more ram than the 2343?