public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: jlarmour@cygnus.co.uk (Jonathan Larmour)
To: brendan@dgs.monash.edu.au
Cc: binutils <binutils@sourceware.cygnus.com>,
	Dan Malek <dmalek@jlc.net>,
	Magnus Damm <eramdam@kieray1.p.y.ki.era.ericsson.se>,
	gdb <gdb@sourceware.cygnus.com>
Subject: Re: objdump or gdb to force a section to load ?
Date: Thu, 01 Jul 1999 00:00:00 -0000	[thread overview]
Message-ID: <199906171606.RAA15562@peshwari.cygnus.co.uk> (raw)
In-Reply-To: <37685993.EB50E446@dgs.monash.edu.au>

In article < 37685993.EB50E446@dgs.monash.edu.au > you write:
>I sent this a while ago and got no response.  I'm resending it just in case
>it got lost.

All of 24 hours before. Perhaps you need to be more patient.

>> I have a linux kernel compiled for a mpc860 target and am trying to get
>> it to run by downloading it into memory using a background debugger
>> (BDM).  The boot code gets to the point where it trys to uncompress the
>> kernel but fails because the image isn't loaded into memory (only .text,
>> .rodata and .data are loaded).  I tried using objcopy to set the "image"
>> section to "load" but it does not seem to work.  How can I get gdb to
>> load the image section (either using a gdb command or binutils) ?

If it isn't marked as loadable, then you probably can't. It hasn't even got
an address for it to be loaded into. If it is to be loaded then it is the
build process (using the linker script) that has to make it loadable.

Perhaps an easier approach would be to use an uncompressed kernel rather than
a zImage.

A ppc-linux list may be able to give more specific advice about why the
linker scripts are the way they are.

Jifl
-- 
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK.  Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
 my brains kept falling out."    || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/  These opinions are all my own fault

  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 Using objdump to force a section to load with gdb Brendan Simon
1999-07-01  0:00 ` objdump or gdb to force a section to load ? Brendan Simon
1999-07-01  0:00   ` Jonathan Larmour [this message]
     [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
1999-07-01  0:00 ` Using objdump to force a section to load with gdb Ian Lance Taylor
1999-07-01  0:00   ` 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=199906171606.RAA15562@peshwari.cygnus.co.uk \
    --to=jlarmour@cygnus.co.uk \
    --cc=binutils@sourceware.cygnus.com \
    --cc=brendan@dgs.monash.edu.au \
    --cc=dmalek@jlc.net \
    --cc=eramdam@kieray1.p.y.ki.era.ericsson.se \
    --cc=gdb@sourceware.cygnus.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).