Stack trace when debugging?

Go To Last Post
4 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Is this possible? I've spent most of a day debugging a problem that a stack trace would have fixed in minutes.

I'm using an xmega chip with a jtagice2.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Nope. Your best bet is to examine the memory in the region of SP and use a copy of the .map file alongside - you may be able to spot obvious return addresses and which function they reside in.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Maybe Atmel should have disabled the stack trace window, so I wouldn't get my hopes up :(

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The stack trace doesn't work yet, it only shows the current call, and doesn't unwind the stack from the entry point in main(). Let's hope for a fix in the update to AVR Studio 5 (but don't hold your breath).
Jerry