From: David Anderson <davea42@earthlink.net>
To: Daniel Jacobowitz <dan@codesourcery.com>
Cc: Jimb@codesourcery.com, julian@codesourcery.com,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Accept DWARF 3-format debug info
Date: Fri, 09 Jun 2006 23:18:00 -0000 [thread overview]
Message-ID: <1149894888.7813.35.camel@quasar2> (raw)
Damiel writes, about a supposed change in DW_FORM_ref_addr:
>References that use the attribute form DW_FORM_ref_addr are specified
>to be four bytes in the DWARF 32-bit format and eight bytes in
the
>DWARF 64-bit format, while DWARF Version 2 specifies that such
>references have the same size as an address on the target
system >(see Sections 7.4 and 7.5.4).
This is a correct observation, but *the dwarf 2 document was wrong*.
We did this late in 1992 and simply botched the document.
Confusion and tiredness :-(
Same size as an address simply makes no sense, never did.
Till very recently I don't think anyone used DW_FORM_ref_addr.
I did get an inquiry from one person (about dwarfdump) that proved
one compiler supplier believes the dwarf2 document on this point. Recent
inquiry, I mean.
There should still be FAQ on dwarf.freestandards.org which
says the DWARF2 doc was/is wrong (I wrote that FAQ).
What the dwarf3 doc says is what we always intended. It's an offset,
not an address. Misleading name of the form...
David Anderson (davea@sgi.com, writing from home)
next reply other threads:[~2006-06-09 23:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 23:18 David Anderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-08 22:48 Julian Brown
2006-06-08 23:25 ` Jim Blandy
2006-06-08 23:59 ` Daniel Jacobowitz
2006-06-18 1:10 ` Mark Kettenis
2006-06-18 4:40 ` Jim Blandy
2006-06-09 7:29 ` Eli Zaretskii
2006-06-09 12:25 ` Daniel Jacobowitz
2006-06-09 16:42 ` Eli Zaretskii
2006-06-09 17:20 ` Daniel Jacobowitz
2006-06-09 19:46 ` Eli Zaretskii
2006-06-09 12:39 ` Julian Brown
2006-06-09 16:39 ` Eli Zaretskii
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=1149894888.7813.35.camel@quasar2 \
--to=davea42@earthlink.net \
--cc=Jimb@codesourcery.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=julian@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