Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Matt Kern <matt.kern@undue.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: DWARF2 FDE Address Mismatch
Date: Tue, 05 Jun 2007 10:37:00 -0000	[thread overview]
Message-ID: <20070605103717.GA29353@pling.qwghlm.org> (raw)
In-Reply-To: <20070601171454.GA4992@them.org>

Okay -- I have a patch which works for our arch.  I haven't tested it on
a stable arch yet though to ensure it doesn't break anything.

The change is to call read_encoded_value() if eh_frame_p is set;
otherwise dwarf2_read_address() is called.  I have modified
dwarf2_read_address to read addresses of size TARGET_ADDR_BIT rather
than TARGET_INT_BIT.

> For .eh_frame we have to do this funny dance with GCC to determine the
> "right" behavior.  For .debug_frame, there is a standard and we should
> be following it - and so should GCC.  What does it have to say?  If it
> says "the size of an address on the target machine" then we should
> probably use TARGET_ADDR_BIT; otherwise I'm not sure.  I think this
> format ambiguity has come up before.

From "7.5.4 Attribute Encodings":

"address     Represented as an object of appropriate size to hold an
             address on the target machine (DW_FORM_addr)."

Matt

-- 
Matt Kern
http://www.undue.org/


      reply	other threads:[~2007-06-05 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 12:20 Matt Kern
2007-06-01 13:44 ` Daniel Jacobowitz
2007-06-01 14:26   ` Matt Kern
2007-06-01 14:55     ` Matt Kern
2007-06-01 17:14     ` Daniel Jacobowitz
2007-06-05 10:37       ` Matt Kern [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=20070605103717.GA29353@pling.qwghlm.org \
    --to=matt.kern@undue.org \
    --cc=drow@false.org \
    --cc=gdb@sourceware.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