From: Tom Tromey <tromey@adacore.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Tom Tromey <tromey@adacore.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: 4b610737f02 Handle copy relocations
Date: Tue, 18 Oct 2022 08:38:35 -0600 [thread overview]
Message-ID: <87v8ohi4d0.fsf@tromey.com> (raw)
In-Reply-To: <DM8PR11MB5749AE94C31F5C35BC08F883DE289@DM8PR11MB5749.namprd11.prod.outlook.com> (Markus T. Metzger's message of "Tue, 18 Oct 2022 13:25:28 +0000")
> 4b610737f02 Handle copy relocations
> With linker namespaces, however, it may cause a wrong address to be
> read after symbol lookup actually found the correct symbol. This can
> be seen, for example, with gdb.base/dlmopen.exp when compiled with
> clang.
> Do you maybe see a different way of supporting copy relocations that
> would not require fixing up the symbol when querying its address?
I'm not really sure how this ought to work when there are linker
namespaces, but basically what gdb needs to do is mimic whatever ldd
does in this situation.
I think copy relocations by their nature require some kind of symbol
search.
Tom
prev parent reply other threads:[~2022-10-18 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 13:25 Metzger, Markus T
2022-10-18 13:25 ` Metzger, Markus T
2022-10-18 14:38 ` Tom Tromey [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=87v8ohi4d0.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.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).