From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org,
Paul Pluzhnikov <ppluzhnikov@google.com>,
Pedro Alves <pedro@codesourcery.com>
Subject: Re: [patch 3/3] Implement qXfer:libraries for Linux/gdbserver #2
Date: Wed, 12 Oct 2011 20:22:00 -0000 [thread overview]
Message-ID: <20111012202204.GA22522@host1.jankratochvil.net> (raw)
In-Reply-To: <CAN9gPaFqp3y7eR14-YftPvCdzubZb4Kz3soLeAVSDN=NMpg8_A@mail.gmail.com>
On Mon, 10 Oct 2011 04:43:36 +0200, Daniel Jacobowitz wrote:
> I would be a whole lot happier if we could use the same <library-list>
> elements for SVR4. There may be some creative interpretations we can
> use to make it work... yes, we'd likely have to pass the link map
> addresses as additional information; fortunately that's easy. I'm not
> sure I understand the issue with dealing with absolute library base
> addresses.
> But in short, the way to think about this is to move all
> the complicated bits of library processing to the target agent, and
> give GDB a simplified view of what's really going on.
The problem is the host symbol file may be also prelinked, therefore there
still needs to be the relocation on gdb side, whether the single number covers
just the host displacement or a sum of both the host and target displacement
does not matter much.
Just this case:
[patch] [i386] Fix {,un}prelinked libraries for attach/core-load
http://sourceware.org/ml/gdb-patches/2011-02/msg00630.html
had to be made in a heuristic way while with using /proc/PID/maps on the
gdbserver Linux side for absolute addresses normalization it could be made
reliable. Going to try it.
> If that's not practical, then +1 to Pedro's suggestion; if you're
> bulk-reading the link maps, or doing some svr4-specific semantics, we
> should express it that way.
If the addresses are absolute then we can just add new attributes to the
current <library-list/> format and I assume the Pedro's suggestion for an
incompatible format is no longer valid then.
Thanks,
Jan
prev parent reply other threads:[~2011-10-12 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 21:55 Jan Kratochvil
2011-10-04 6:11 ` Eli Zaretskii
2011-10-18 17:49 ` Messages localization in gdbserver [Re: [patch 3/3] Implement qXfer:libraries for Linux/gdbserver #2] Jan Kratochvil
2011-10-06 19:09 ` [patch 3/3] Implement qXfer:libraries for Linux/gdbserver #2 Pedro Alves
2011-10-21 11:05 ` Jan Kratochvil
2011-10-21 13:32 ` Pedro Alves
2011-11-03 21:30 ` [patch] Implement qXfer:libraries-svr4 for Linux/gdbserver #4 Jan Kratochvil
2011-12-02 22:33 ` [commit] " Jan Kratochvil
2011-12-03 17:03 ` Doug Evans
2011-12-03 18:34 ` [commit] Fix compilation --without-expat [Re: [commit] [patch] Implement qXfer:libraries-svr4 for Linux/gdbserver #4] Jan Kratochvil
2011-10-10 2:44 ` [patch 3/3] Implement qXfer:libraries for Linux/gdbserver #2 Daniel Jacobowitz
2011-10-12 20:22 ` Jan Kratochvil [this message]
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=20111012202204.GA22522@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=ppluzhnikov@google.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