From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17075 invoked by alias); 2 May 2010 19:54:49 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Received: (qmail 17064 invoked by uid 22791); 2 May 2010 19:54:48 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Subject: Re: Size of DW_FORM_ref_addr in DWARF 3 and the archer-jankratochvil-fedora13 branch From: Joost van der Sluis To: Jan Kratochvil Cc: archer@sourceware.org In-Reply-To: <20100429173916.GA6347@host0.dyn.jankratochvil.net> References: <1271777933.28610.63.camel@wsjoost.cnoc.lan> <20100429173916.GA6347@host0.dyn.jankratochvil.net> Content-Type: text/plain Date: Sun, 02 May 2010 19:54:00 -0000 Message-Id: <1272830065.20542.2.camel@wsjoost.cnoc.lan> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Language-Detected: en X-Spam-Scanned: InterNLnet Mail Scan System V2.03 X-SW-Source: 2010-q2/txt/msg00018.txt.bz2 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 > Date: Thu Mar 4 22:01:09 2010 +0000 > > * dwarf2read.c (skip_one_die) : Use offset size > in DWARF 3 and later. > (read_attribute_value) : Likewise. > > checked-in after gdb_7_1-branch has been created but still before the 7.1 > release by: > > commit c6c011eebb4006a89d4344864f560762f0aa45f3 > Author: Tom Tromey > Date: Fri Mar 5 15:37:33 2010 +0000 > > * dwarf2read.c (skip_one_die) : Use offset size > in DWARF 3 and later. > (read_attribute_value) : 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.