Stack trace when debugging?

Log in or register to post comments
Go To Last Post
4 posts / 0 new
Author
Message
lagger
lagger's picture
Level: Hangaround
Joined: Sun. Sep 4, 2005
Posts: 194 View posts
#1
Posted by lagger: Tue. Oct 18, 2011 - 07:44 PM
  • 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.

Tags:

Tools, Atmel Studio (AVR-related)
Top
Gold Markclawson
clawson's picture
Level: Moderator
Joined: Mon. Jul 18, 2005
Posts: 101136 View posts
Location: (using avr-gcc in) Finchingfield, Essex, England
Posted by clawson: Tue. Oct 18, 2011 - 07:52 PM
  • 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.

Top
lagger
lagger's picture
Level: Hangaround
Joined: Sun. Sep 4, 2005
Posts: 194 View posts
Posted by lagger: Wed. Oct 19, 2011 - 08:04 AM
  • 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 :(

Top
jerryr
jerryr's picture
Level: Hangaround
Joined: Fri. Apr 23, 2004
Posts: 368 View posts
Location: Liederbach; Germany
Posted by jerryr: Fri. Oct 21, 2011 - 09:30 AM
  • 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

Top