From: Roland McGrath <roland@redhat.com>
To: Ian Lance Taylor <ian@airs.com>
Cc: Nick Clifton <nickc@redhat.com>,
binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: bfd function to read ELF file image from memory
Date: Mon, 19 May 2003 20:46:00 -0000 [thread overview]
Message-ID: <200305192046.h4JKkH713031@magilla.sf.frob.com> (raw)
In-Reply-To: Ian Lance Taylor's message of , 19 May 2003 13:29:58 -0700 <m38yt2he7t.fsf@gossamer.airs.com>
> You could do something like that, assuming you put the appropriate hook
> in the elf_backend_data struct, which is less intrusive than putting it
> in the bfd_target struct.
Aha! That is the pointer I was looking for.
Thanks,
Roland
next prev parent reply other threads:[~2003-05-19 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 1:28 Roland McGrath
2003-05-16 11:24 ` Nick Clifton
2003-05-16 21:30 ` Roland McGrath
2003-05-19 10:29 ` Nick Clifton
2003-05-19 20:24 ` Roland McGrath
2003-05-19 20:30 ` Ian Lance Taylor
2003-05-19 20:46 ` Roland McGrath [this message]
2003-05-17 5:39 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 1:20 Roland McGrath
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=200305192046.h4JKkH713031@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=ian@airs.com \
--cc=nickc@redhat.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