From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17104 invoked by alias); 5 Feb 2002 16:39:12 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 17041 invoked from network); 5 Feb 2002 16:39:08 -0000 Received: from unknown (HELO lacrosse.corp.redhat.com) (12.107.208.154) by sources.redhat.com with SMTP; 5 Feb 2002 16:39:08 -0000 Received: from redhat.com (IDENT:root@tooth.toronto.redhat.com [172.16.14.29]) by lacrosse.corp.redhat.com (8.11.6/8.9.3) with ESMTP id g15Gd6I23829 for ; Tue, 5 Feb 2002 11:39:06 -0500 Message-ID: <3C600AC0.417C922E@redhat.com> Date: Tue, 05 Feb 2002 08:39:00 -0000 From: Dave Brolley X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i686) X-Accept-Language: en MIME-Version: 1.0 To: sid@sources.redhat.com Subject: Re: SID ELF loader using wrong load address? References: <3C5EEF5F.77116D06@redhat.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-q1/txt/msg00025.txt.bz2 Approved by fche and committed. Dave Brolley wrote: > Hi, > > I have a linker script for an application on an ELF target which > contains something like the following: > > .reloc_section 0x1000 : AT (LOADADDR(.text)+SIZEOF(.text)) > { > *(.reloc_section) > } > > This is a section of code which should be loaded at the end of the .text > section and is intended to be copied (by the application itself) to > address 0x1000 before being executed. However, the SID ELF loader > currently loads this section at address 0x1000 (the VMA) instead of at > the given LMA. Visual inspection of a hex dump of my executable shows > that, for elf32, the address being used at offset 8 of the section > header is indeed the VMA and that the LMA is at offset 12 (can anyone > confirm this?). > > The attached patch gets the section loaded at the proper LMA and has > been tested against my port (an internal one) and against xstormy16. I > would not expect any regressions since the LMA and the VMA are the same > unless one plays linker script tricks like the one above. > > OK to commit? > > Dave > > ------------------------------------------------------------------------ > Name: lma.ChangeLog > lma.ChangeLog Type: Plain Text (text/plain) > Encoding: 7bit > > Name: lma.patch.txt > lma.patch.txt Type: Plain Text (text/plain) > Encoding: 7bit