From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: schwab@suse.de
Cc: gdb-patches@sourceware.org
Subject: Re: .eh_frame vs. .debug_frame register encoding
Date: Tue, 09 May 2006 19:58:00 -0000 [thread overview]
Message-ID: <200605091957.k49JvkSQ029319@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <jelktb1ee9.fsf@sykes.suse.de> (message from Andreas Schwab on Tue, 09 May 2006 16:06:22 +0200)
> From: Andreas Schwab <schwab@suse.de>
> Date: Tue, 09 May 2006 16:06:22 +0200
>
> On powerpc the register encoding inside .eh_frame differs from the one in
> .debug_frame. The former is using GCC internal numbering, whereas the
> latter is (of course) using the DWARF numbering. So when gdb is reading
> .eh_frame it needs to translate the register numbers (one important
> difference is that the lr register has a different encoding). This is a
> prerequisite for using the DWARF CFI unwinder on powerpc.
Looks reasonable to me.
> 2006-05-09 Andreas Schwab <schwab@suse.de>
>
> * dwarf2-frame.c (struct dwarf2_fde): Add eh_frame_p.
> (execute_cfa_program): Add parameter eh_frame_p. Call
> dwarf2_frame_eh_frame_regnum when true.
> (dwarf2_frame_cache): Pass eh_frame_p from fde to
> execute_cfa_program.
> (decode_frame_entry_1): Call dwarf2_frame_eh_frame_regnum when
> processing .eh_frame. Copy eh_frame_p to the new fde.
> (struct dwarf2_frame_ops): Add eh_frame_regnum.
> (dwarf2_frame_set_eh_frame_regnum): Define.
> (dwarf2_frame_eh_frame_regnum): Define.
>
> * dwarf2-frame.h (dwarf2_frame_set_eh_frame_regnum): Declare.
> (dwarf2_frame_eh_frame_regnum): Declare.
prev parent reply other threads:[~2006-05-09 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 14:06 Andreas Schwab
2006-05-09 19:58 ` Mark Kettenis [this message]
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=200605091957.k49JvkSQ029319@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=schwab@suse.de \
/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