From: Daniel Jacobowitz <drow@false.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Generic support for qGetTLSAddr packet
Date: Wed, 08 Dec 2004 01:39:00 -0000 [thread overview]
Message-ID: <20041208003756.GA29715@nevyn.them.org> (raw)
In-Reply-To: <20041207172410.36b8e046.kevinb@redhat.com>
On Tue, Dec 07, 2004 at 05:24:10PM -0700, Kevin Buettner wrote:
> > So, unless I completely misunderstood what you had in mind, I'm not
> > in favor of the to_xfer_partial approach.
I thought about it some more also; I think your analysis was right,
there's not much to gain here. Except... (see bottom).
> It's just occurred to me that the encoding of thread-id and
> load-module into annex could also handle any necessary OS/ABI related
> translations of the load module. This means that that we wouldn't
> need two separate code paths which both call
> svr4_fetch_objfile_link_map().
>
> Of course, the load module translation could also be done (assuming an
> interface change) prior to the call to_get_thread_local_address().
> I think this would address both Mark's and Andrew's comments about
> remote.c doing somewhat more than expected.
>
> I'll mull it over some more...
Another thing I was thinking about was the usefulness of
target-agnostic code for this - I think, very small. We know what the
get-tls-address operation looks like for GNU/Linux, but not (at least
not I) for any other system. Presumably there's some way to do this on
Solaris too.
Pending more systems with similar problems, it would be nice if we
could organize all the logic into target-specific code. Here's where
using target_xfer_partial would be convenient. I visualize something
like this:
linux-nat.c provides to_xfer_partial, which can provide X
linux-tdep.c overrides remote.c's to_xfer_partial (this would
require a bit of fiddling - I think the best way would be to steer
clear of target inheritance, and use a gdbarch hook called from
the remote.c version), with another method for providing X
What the arguments to X should look like, I'm not sure. It would be
nice to pass the objfile directly, but the to_xfer_partial interface is
not friendly to that; it would be logical to pass the link map address,
but that breaks the abstraction.
Hmm....
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-12-08 0:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 21:57 Kevin Buettner
2004-12-06 22:51 ` Mark Kettenis
2004-12-06 23:06 ` Daniel Jacobowitz
2004-12-08 0:24 ` Kevin Buettner
2004-12-08 0:38 ` Kevin Buettner
2004-12-08 1:39 ` Daniel Jacobowitz [this message]
2004-12-06 23:46 ` Kevin Buettner
2004-12-12 18:17 ` Andrew Cagney
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=20041208003756.GA29715@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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