From: Andrew Cagney <ac131313@redhat.com>
To: "Theodore A. Roth" <troth@openavr.org>
Cc: gdb@sources.redhat.com
Subject: Re: avr and frame unwinding
Date: Fri, 06 Jun 2003 02:01:00 -0000 [thread overview]
Message-ID: <3EDFF5D5.5060704@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0306051719070.29024@knuth.amplepower.com>
Can you try the exact same operation with a GDB that doesn't have the
changes? That way it should be possible to compare the two traces
side-by-side and see where things are going wrong.
A guess is that it is getting the unwound PC value wrong. For the d10v
I had to make two tweaks:
- abort the prologue scanner when it reached PC if that is before the
end of the prologue
This stopped the prologue getting the unwound PC's location wrong. It
may not have yet executed the save PC instruction.
- track the register that the PC is in before it is saved
The code needs to be able to unwind the PC value in the prologue before
it has been saved on the stack.
Andrew
next prev parent reply other threads:[~2003-06-06 2:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 0:35 Theodore A. Roth
2003-06-06 2:01 ` Andrew Cagney [this message]
2003-06-07 20:23 ` Theodore A. Roth
2003-06-07 22:37 ` Andrew Cagney
2003-06-08 0:26 ` Theodore A. Roth
2003-06-08 17:51 ` Theodore A. Roth
2003-06-08 19:15 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EDFF5D5.5060704@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=troth@openavr.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).