public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: brendan@dgs.monash.edu.au
Cc: jlarmour@cygnus.co.uk, eramdam@kieray1.p.y.ki.era.ericsson.se,
	dmalek@jlc.net, gdb@sourceware.cygnus.com,
	binutils@sourceware.cygnus.com
Subject: Re: SOLVED: objdump or gdb to force a section to load ?
Date: Thu, 01 Jul 1999 00:00:00 -0000	[thread overview]
Message-ID: <19990618052740.26680.qmail@daffy.airs.com> (raw)
In-Reply-To: <376996F2.1F150FCF@dgs.monash.edu.au>

   Date: Fri, 18 Jun 1999 00:46:42 +0000
   From: Brendan Simon <brendan@dgs.monash.edu.au>

   I tried a few combinations and found that
   "--set-section-flags=image=load,alloc,readonly" does work even thought it complains
   with "BFD: sta00639: warning: allocated section `image' not in segment".

Yeah, this is what I meant in my previous message about getting
loadable information from the segments rather than the sections.

This is an area where it is hard for BFD to hide the specific
characteristics of ELF.

Ian

  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
     [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 [this message]
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=19990618052740.26680.qmail@daffy.airs.com \
    --to=ian@zembu.com \
    --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 \
    --cc=jlarmour@cygnus.co.uk \
    /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).