From: Alexandre Oliva <aoliva@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com, cagney@redhat.com
Subject: Re: cope with varying prelink base addresses
Date: Fri, 10 Feb 2006 00:15:00 -0000 [thread overview]
Message-ID: <or8xsk83yj.fsf@livre.oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <u1wye5pvl.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 08 Feb 2006 08:25:02 +0200")
On Feb 8, 2006, Eli Zaretskii <eliz@gnu.org> wrote:
> Would it make sense to add a user command/variable that will tell GDB
> the difference between the two base addresses?
Err... Not really. Unless you mean some per-dynamic-object setting.
And I really think it's overkill.
Perhaps it migth make sense to ask the user what to do whenever we
detect an inconsistency between the expected address of l_ld and the
address it is on, offering a reasonable default, but even that is
probably overkill, and it might change the behavior if l_ld doesn't
mean what we think it does.
Besides, we already sort-of have the means to do it. GDB has commands
to set the addresses of individual sections. It would be a pain, but
it can be done.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
Secretary for FSF Latin America http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2006-02-10 0:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 5:35 Alexandre Oliva
2006-02-08 6:25 ` Eli Zaretskii
2006-02-10 0:15 ` Alexandre Oliva [this message]
2006-02-08 21:40 ` Mark Kettenis
2006-02-10 0:09 ` Alexandre Oliva
2006-02-10 1:42 ` Daniel Jacobowitz
2006-02-13 19:03 ` Alexandre Oliva
2006-02-14 0:56 ` Kevin Buettner
2006-02-14 2:08 ` Daniel Jacobowitz
2006-02-14 18:40 ` Alexandre Oliva
2006-02-14 18:53 ` Mark Kettenis
2006-02-20 18:16 ` Alexandre Oliva
2006-02-20 21:49 ` Mark Kettenis
2006-02-20 17:37 ` Daniel Jacobowitz
2006-02-20 17:43 ` Daniel Jacobowitz
2006-02-23 20:22 ` Alexandre Oliva
2006-02-23 20:53 ` Daniel Jacobowitz
2006-02-24 7:42 ` Alexandre Oliva
2006-02-28 1:50 ` Kevin Buettner
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=or8xsk83yj.fsf@livre.oliva.athome.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=cagney@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.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