From: Eli Zaretskii <eliz@gnu.org>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gdb-patches@sources.redhat.com, cagney@redhat.com
Subject: Re: cope with varying prelink base addresses
Date: Wed, 08 Feb 2006 06:25:00 -0000 [thread overview]
Message-ID: <u1wye5pvl.fsf@gnu.org> (raw)
In-Reply-To: <ormzh2zawm.fsf@livre.oliva.athome.lsd.ic.unicamp.br> (message from Alexandre Oliva on Wed, 08 Feb 2006 03:18:01 -0200)
> From: Alexandre Oliva <aoliva@redhat.com>
> Date: Wed, 08 Feb 2006 03:18:01 -0200
>
> The only piece of information available for this that I could find was
> the address of the dynamic table in the dynamic loader data
> structures. The heuristics I used was to check whether the dynamic
> table address changed but remained at the same position within a
> page. If so, I assume the difference is caused by prelinking, and
> then I adjust the load_addr that gdb is going to use for that binary.
> Otherwise, it will face the same problems you're expected to face when
> debugging a core file using a different binary.
Would it make sense to add a user command/variable that will tell GDB
the difference between the two base addresses? I guess it would be a
good idea if the user has a way of finding out this number by some
means that are unavailable to GDB (e.g., by gaining access to the
other machine or talking to someone sitting in front of it).
WDYT?
next prev parent reply other threads:[~2006-02-08 6:25 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 [this message]
2006-02-10 0:15 ` Alexandre Oliva
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=u1wye5pvl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aoliva@redhat.com \
--cc=cagney@redhat.com \
--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