From: Brendan Simon <brendan@dgs.monash.edu.au>
To: Ian Lance Taylor <ian@zembu.com>,
binutils <binutils@sourceware.cygnus.com>
Subject: Re: Using objdump to force a section to load with gdb.
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <3769EC4D.99196D87@dgs.monash.edu.au> (raw)
In-Reply-To: <19990618052534.26635.qmail@daffy.airs.com>
Ian Lance Taylor wrote:
> The problem with using objcopy to set the LOAD flag is that the only
> sections which are loaded are those which are stored in program
> segments. objcopy isn't prepared to create a new program segment in
> order to change a section flag. This would be difficult to fix.
>
> If your loader reads the section headers rather than the segment
> headers, then you may be able to make this work by doing something
> like
> powerpc-linux-objcopy --set-section-flags=image=alloc,load myzimage
> The reason is that ELF records the ALLOC flag in the section header,
> and objcopy should know how to change that.
>
> The best way to make a loadable section is to mark the section as
> loadable in the first place. See the gas documentation for how to set
> the section flags when using the .section directive.
I'm not sure if this is applicable when the section is added with "objcopy
--add-section=image=vmlinux.gz", where vmlinux.gz is an elf file that has been
compressed with gzip. How does one add this file as a section to an existing
elf file (bootloader) as "loadable in the first place" ?
Brendan Simon.
next prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Brendan Simon
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Brendan Simon [this message]
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` objdump or gdb to force a section to load ? Brendan Simon
1999-07-01 0:00 ` Jonathan Larmour
[not found] ` <376981EF.BE10D7C8@dgs.monash.edu.au>
[not found] ` <37699391.2CF83050@cygnus.co.uk>
1999-07-01 0:00 ` SOLVED: " Brendan Simon
1999-07-01 0:00 ` Ian Lance Taylor
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=3769EC4D.99196D87@dgs.monash.edu.au \
--to=brendan@dgs.monash.edu.au \
--cc=binutils@sourceware.cygnus.com \
--cc=ian@zembu.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).