From: Camm Maguire <camm@enhanced.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: binutils@sources.redhat.com
Subject: BFD relocations
Date: Sun, 02 Jun 2002 20:42:00 -0000 [thread overview]
Message-ID: <E17Eijt-0001Sw-00@intech19.enhanced.com> (raw)
Greetings! I saw your post about bfd_get_relocated_section_contents
usage in gdb, and was pleasantly surprised that you had found the same
approach I've been trying to implement over the past few days in gcl
for loading, relocating, and executing objects at runtime in Lisp.
Problem is, it only seems to work in x86 :-(, at least as far as I can
tell. Kind of defeats the purpose of using bfd for portability :-).
I've gone through the mips case in detail, and one cannot even call
this routine unless one sets the relocateable argument to true, as it
will result in trying to call _bfd_get_gp_value with a null
argument. Likewise on ppc, the relocation apparently succeeds, but
the source is not correctly relocated. I've noticed that ld doesn't
seem to actually use this routine, but rather uses a variety of
backend specific routines ...._relocate_section. Arguments to this no
longer seem canonical, alas.
Just wanted to tap your experience. Have you tested your gdb patch on
other archs? Any work beside x86? Is there another path through the
bfd labyrinth that would simply allow one to load a correctly relocated
section at an arbitrary address, after defining the symbols of course?
Any help most appreciated!
--
Camm Maguire camm@enhanced.com
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
next reply other threads:[~2002-06-03 3:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 20:42 Camm Maguire [this message]
2002-06-02 22:06 ` Daniel Jacobowitz
2002-06-03 15:08 ` Camm Maguire
2002-06-03 15:29 ` Daniel Jacobowitz
2002-06-04 14:34 ` [Gcl-devel] " Camm Maguire
2002-06-04 14:42 ` Geoff Keating
2002-06-04 14:44 ` Daniel Jacobowitz
2002-06-04 15:06 ` Camm Maguire
2002-06-04 15:33 ` Daniel Jacobowitz
2002-06-05 16:03 ` Camm Maguire
2002-06-05 16:09 ` Daniel Jacobowitz
2002-06-05 17:21 ` Camm Maguire
2002-06-05 18:13 ` Daniel Jacobowitz
2002-06-06 20:14 ` Camm Maguire
2002-06-06 21:00 ` Daniel Jacobowitz
2002-06-06 22:03 ` Jason R Thorpe
2002-06-07 6:55 ` Paul Koning
2002-06-10 15:35 ` Camm Maguire
2002-06-10 16:10 ` Daniel Jacobowitz
2002-06-14 8:51 ` Flushing the d-cache (was Re: BFD relocations) Camm Maguire
2002-06-14 9:16 ` Philip Blundell
2002-06-14 12:22 ` [Gcl-devel] " Camm Maguire
2002-06-14 12:34 ` Philip Blundell
2002-06-14 13:10 ` Andreas Schwab
2002-06-17 15:37 ` Richard Zidlicky
2002-06-17 20:09 ` [Gcl-devel] " Camm Maguire
2002-06-19 11:25 ` MIPS bfd_get_relocated_section_contents broken Camm Maguire
2002-07-27 0:06 ` [Gcl-devel] Re: BFD relocations Camm Maguire
2002-07-27 9:08 ` Alan Modra
2002-07-27 12:23 ` Camm Maguire
2002-07-30 0:46 ` Alan Modra
2002-08-11 9:26 ` BFD relocations -- alpha Camm Maguire
2002-06-05 20:09 ` [Gcl-devel] Re: BFD relocations Geoff Keating
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=E17Eijt-0001Sw-00@intech19.enhanced.com \
--to=camm@enhanced.com \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.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).