From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: GDB <gdb@sources.redhat.com>
Subject: Re: Invalid registers
Date: Tue, 12 Jul 2005 17:34:00 -0000 [thread overview]
Message-ID: <20050712173450.GA1486@nevyn.them.org> (raw)
In-Reply-To: <op.sts5l3b3o669wz@terrorhawk.bri.st.com>
On Tue, Jul 12, 2005 at 05:04:41PM +0100, Andrew STUBBS wrote:
> Thank you. This has helped me find the right stuff to look at.
>
> I do not think I actually want to use dwarf2_frame_set_init_reg. The
> compiler (GCC 3.4.3) produces CFI information which I think ought to be
> enough.
>
> The function execute_cfa_program in dwarf2-frame.c appears to load all the
> relevant data (setting breakpoints in strategic places show this). If I
> use 'up' and 'info registers' I see the values change, which shows that
> the CFI data has been loaded (doesn't it?). It just appears that the 'how'
> field from the CFA is being ignored when the values are printed. Setting
> 'how' via dwarf2_frame_set_init_reg is not ignored however. It must be
> being reset, or perhaps not copied in the first place.
>
> Any clues?
Sorry, not enough information - I'd need specifics. GCC's CFI
generally does not represent call-clobbered registers; waste of space
for a runtime unwinder.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-12 17:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 15:42 Andrew STUBBS
2005-07-11 15:49 ` Daniel Jacobowitz
2005-07-11 18:47 ` Marcel Moolenaar
2005-07-11 18:51 ` Daniel Jacobowitz
2005-07-11 19:08 ` Marcel Moolenaar
2005-07-12 16:16 ` Andrew STUBBS
2005-07-12 17:19 ` Marcel Moolenaar
2005-07-12 16:07 ` Andrew STUBBS
2005-07-12 17:34 ` Daniel Jacobowitz [this message]
2005-07-13 15:13 ` Andrew STUBBS
2005-07-13 15:42 ` Daniel Jacobowitz
2005-07-13 16:16 ` Andrew STUBBS
2005-07-13 20:27 ` Daniel Jacobowitz
2005-07-14 9:36 ` Andrew STUBBS
2005-07-14 14:11 ` Daniel Jacobowitz
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=20050712173450.GA1486@nevyn.them.org \
--to=drow@false.org \
--cc=andrew.stubbs@st.com \
--cc=gdb@sources.redhat.com \
/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).