From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: RFC: fix misplaced .note.gnu.build-id section
Date: Fri, 21 May 2010 19:43:39 +0100 [thread overview]
Message-ID: <20100521184339.GA11042@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100521133612.GA30171@sig21.net>
On Fri, May 21, 2010 at 03:36:12PM +0200, Johannes Stezenbach wrote:
> when building with a binutils version which supports --build-id
> the .note.gnu.build-id section is placed at address 0 in the
> resulting vmlinux ELF file:
>
> Program Header:
> LOAD off 0x00008000 vaddr 0x00000000 paddr 0x00000000 align 2**15
> filesz 0x00000024 memsz 0x00000024 flags r--
> LOAD off 0x00010000 vaddr 0xc0008000 paddr 0xc0008000 align 2**15
> filesz 0x0033cb60 memsz 0x0036df04 flags rwx
> NOTE off 0x00008000 vaddr 0x00000000 paddr 0x00000000 align 2**2
> filesz 0x00000024 memsz 0x00000024 flags r--
There seems to be little reason for the note to be loaded into memory -
maybe the right fix is to ensure that the note doesn't get placed into
a loadable output section.
next prev parent reply other threads:[~2010-05-21 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 13:36 RFC: fix misplaced .note.gnu.build-id section Johannes Stezenbach
2010-05-21 18:43 ` Russell King - ARM Linux [this message]
2010-05-21 20:22 ` Johannes Stezenbach
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=20100521184339.GA11042@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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 NNTP newsgroup(s).