AVR-Chat

Agree, but....

I think this is an inherent limit due to JTAG debugging. You don't get
history information out of JTAG. You just get the current state at the
breakpoint. The "alternative" would be single-step operation, which would
hardly be "real-time", due to the less than speedy traffic on the JTAG
link.

Jim Wagner
Oregon Research Electronics

> --- In AVR-Chat@yahoogroups.com, "Chuck Hackett" <egroupscdh@...> wrote:
>> I'm currently using AVRStudio W/WinAVR but I would like to find a
>> (Windows based) debugger that has things like stack-traceback
> I could be wrong but I believe that avr-gcc doesn't provide the necessary
> debug information to implement backtrace.  Moreover, not every function
> has a frame pointer anyway - only those that require local stack frame
> allocation get a frame pointer.  It might be possible force the compiler
> to generate a frame pointer for each function but you'll pay a penalty in
> code size and speed for this.
>
> There may have been a thread or two recently on this topic at
> avrfreaks.net.  If not, it may be fruitful to post the question there.
>
> I understand why you'd like this capability (I would, too).  I have
> debugged multi-task applications using the AVR Studio debugger without it.
>  You do need to be clever and resourceful on occasion to get the job done.
>
> Don Kinzer
> ZBasic Microcontrollers
> http://www.zbasic.net
>
>