AVR-Chat

The stack trace depends entirely upon how the particular compiler uses it.
GCC, for example, lays out a pretty traditional stack with locals & links.
IAR and ICC both use separate data and call/return stacks.

I bet the native GCC debugger (GDB) does an excellent stack trace... of GCC
code.

-----Original Message-----
From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com]On
Behalf Of Chuck Hackett
Sent: Friday, April 15, 2005 4:34 PM
To: AVR-Chat@yahoogroups.com
Subject: RE: [AVR-Chat] Debugging ATMega16



> From: Ivan Vernot
>
> > ....
> > 1) Is there a way to display the current call-chain (i.e.: stack trace)
> Not with the JTAGICE (you need the ICE50 for that - but there have been
> people in this group saying they the ICE50 is very unstable/buggy)

Strange, I thought stack trace back was a standard feature of symbolic
debuggers.  Is there something about AVRs that makes this difficult?