From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12057 invoked by alias); 28 Dec 2007 14:46:50 -0000 Received: (qmail 12047 invoked by uid 22791); 28 Dec 2007 14:46:50 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 28 Dec 2007 14:46:45 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id lBSEkgIq004171; Fri, 28 Dec 2007 09:46:42 -0500 Received: from pobox.fab.redhat.com (pobox.fab.redhat.com [10.33.63.12]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id lBSEkfEH021136; Fri, 28 Dec 2007 09:46:41 -0500 Received: from [10.32.4.31] (vpn-4-31.str.redhat.com [10.32.4.31]) by pobox.fab.redhat.com (8.13.1/8.13.1) with ESMTP id lBSEke00020633; Fri, 28 Dec 2007 09:46:40 -0500 Message-ID: <47750C68.2060300@redhat.com> Date: Fri, 28 Dec 2007 14:46:00 -0000 From: Nick Clifton User-Agent: Thunderbird 1.5.0.12 (X11/20071018) MIME-Version: 1.0 To: Nick Hudson CC: binutils@sourceware.org Subject: Re: hppa unwind entries References: <200712121318.21023.nick.hudson@dsl.pipex.com> In-Reply-To: <200712121318.21023.nick.hudson@dsl.pipex.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2007-12/txt/msg00155.txt.bz2 Hi Nick, > It seems to me that the calculation of text_segment_base and data_segment_base > are incorrect and here's a patch that address the problem by using the method > ia64 SEGREL stuff is done. > > Is this right? Is there a simpler way? It is correct and no there is isn't a simpler way. I have applied your patch (thanks for creating it by the way) along with this ChangeLog entry. Cheers Nick bfd/ChangeLog 2007-12-28 Nick Hudson * elf32-hppa.c (hppa_record_segment_addr): Locate the segment containing the section using the segment map, rather than guessing based upon the section's vma and file position.