From: Fred Fish <fnf@specifix.com>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org, fnf@specifix.com
Subject: Re: [RFC] DWARF 2 address size != pointer size
Date: Fri, 12 May 2006 14:21:00 -0000 [thread overview]
Message-ID: <200605121020.27657.fnf@specifix.com> (raw)
In-Reply-To: <vt2u07wmbbg.fsf@theseus.home.>
On Thursday 11 May 2006 18:44, Jim Blandy wrote:
> Technically, this isn't quite right, since each CU could potentially
> have a different address size. It's not a global property of the
> debug info.
Correct. I think my patches have a comment related to that.
> Here's the patch; is it addressing the same thing yours does? I'm not
> sure it deals with frame info right, but I'm pretty sure the rest of
> it is going in the right direction:
I tried applying it, but it didn't apply cleanly and I gave up trying
to fix it up after I found out it uses code that was deleted a couple
years ago (dwarf2_pinfo for example).
-Fred
next prev parent reply other threads:[~2006-05-12 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 18:24 Fred Fish
2006-05-11 22:44 ` Jim Blandy
2006-05-12 14:21 ` Fred Fish [this message]
2006-05-12 18:19 ` Jim Blandy
2006-05-12 19:57 ` Mark Kettenis
2006-05-12 20:07 ` Daniel Jacobowitz
2006-05-12 22:32 ` David S. Miller
2006-05-12 22:42 ` 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=200605121020.27657.fnf@specifix.com \
--to=fnf@specifix.com \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.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