From: Joost van der Sluis <joost@cnoc.nl>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: archer@sourceware.org
Subject: Re: Size of DW_FORM_ref_addr in DWARF 3 and the archer-jankratochvil-fedora13 branch
Date: Sun, 02 May 2010 19:54:00 -0000 [thread overview]
Message-ID: <1272830065.20542.2.camel@wsjoost.cnoc.lan> (raw)
In-Reply-To: <20100429173916.GA6347@host0.dyn.jankratochvil.net>
On Thu, 2010-04-29 at 19:39 +0200, Jan Kratochvil wrote:
> On Tue, 20 Apr 2010 17:38:53 +0200, Joost van der Sluis wrote:
> > Since Dwarf 3 the length of a DW_FORM_ref_addr entry is not dependent on
> > the pointer size of the target platform, but on the used Dwarf-format
> > (32 bit or 64 bit) for the current compilation section.
>
> This is a HEAD patch
>
> commit e3fa87d5f376db4523a844acc01199785d11b582
> Author: Tom Tromey <tromey@redhat.com>
> Date: Thu Mar 4 22:01:09 2010 +0000
>
> * dwarf2read.c (skip_one_die) <DW_FORM_ref_addr>: Use offset size
> in DWARF 3 and later.
> (read_attribute_value) <DW_FORM_ref_addr>: Likewise.
>
> checked-in after gdb_7_1-branch has been created but still before the 7.1
> release by:
>
> commit c6c011eebb4006a89d4344864f560762f0aa45f3
> Author: Tom Tromey <tromey@redhat.com>
> Date: Fri Mar 5 15:37:33 2010 +0000
>
> * dwarf2read.c (skip_one_die) <DW_FORM_ref_addr>: Use offset size
> in DWARF 3 and later.
> (read_attribute_value) <DW_FORM_ref_addr>: Likewise.
>
>
> > When I load a project with Dwarf-3 debug information with fsf-gdb head,
> > it works. But not with the archer-jankratochvil-fedora13 branch. That
> > version assumes that the length of a DW_FORM_ref_addr on 64 bit is
> > always 64 bits, which is not the case.
>
> It works with FSF GDB HEAD, FSF GDB 7.1 and Fedora-13 gdb-7.1.
> It does not work with archer-jankratochvil-fedora13 as it is just an
> intermediate step for Fedora-13 gdb-7.1.
>
> Tried now to merge archer-jankratochvil-fedora13 with gdb_7_1-branch but there
> is a problem it would need changes for the FSF-accepted using-directive
> patchset. One cannot cheerry-pick the patch as diff against gdb_7_1-branch
> would then clash on that patch duplicity with FSF 7.1 release.
>
>
> > Is it planned to merge this fix from fsf-gdb to
> > archer-jankratochvil-fedora13? How is this normally handled?
>
> archer-jankratochvil-fedora13 is now probably completely frozen (=dead) as
> I already add rather patches directly to the F-13 CVS. One cannot change F-13
> much as it is far in its release cycle.
>
> There should be some archer-jankratochvil-fedora14 branch created soon
> (=roughly in about two months). I have to admit there is currently no fresh
> Archer-merged branch.
Thanks for the information. As long as this problem is not in Fedora-13
I'm happy.
I can work around this for now. Thanks for the information.
Regards,
Joost.
prev parent reply other threads:[~2010-05-02 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 15:39 Joost van der Sluis
2010-04-29 17:39 ` Jan Kratochvil
2010-05-02 19:54 ` Joost van der Sluis [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=1272830065.20542.2.camel@wsjoost.cnoc.lan \
--to=joost@cnoc.nl \
--cc=archer@sourceware.org \
--cc=jan.kratochvil@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).