From: Daniel Jacobowitz <drow@false.org>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: gdb@sourceware.org, binutils@sourceware.org
Subject: Re: GDB confused by -shared object executable
Date: Fri, 28 Sep 2007 16:29:00 -0000 [thread overview]
Message-ID: <20070928160532.GA14380@caradoc.them.org> (raw)
In-Reply-To: <1190995357.27975.157.camel@murta.transitives.com>
On Fri, Sep 28, 2007 at 05:02:37PM +0100, Alex Bennee wrote:
> Which doesn't seem to work. So questions:
>
> 1. Am I using the correct instantiation to load symbols at a particular
> address?
> 2. Should GDB check the ELF when it loads it to see if it is an
> executable shared object?
Red Hat (Elena, I think) long ago implemented support for PIE in GDB.
What you're doing is basically the same thing. So far, no one has
gotten around to merging that support to the FSF releases.
I think it's in both the Red Hat and Ubuntu packages nowadays.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-09-28 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 16:05 Alex Bennee
2007-09-28 16:29 ` Daniel Jacobowitz [this message]
2007-09-28 16:31 ` Alex Bennee
2007-09-28 17:56 ` Daniel Jacobowitz
2007-10-01 10:22 ` Alex Bennee
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=20070928160532.GA14380@caradoc.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=kernel-hacker@bennee.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