From: Daniel Jacobowitz <drow@false.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc / remote protocol] Remote shared library events
Date: Fri, 11 May 2007 18:21:00 -0000 [thread overview]
Message-ID: <20070511182103.GA2500@caradoc.them.org> (raw)
In-Reply-To: <20070511110250.02dee32c@ironwood.lan>
On Fri, May 11, 2007 at 11:02:50AM -0700, Kevin Buettner wrote:
> On Wed, 9 May 2007 16:16:27 -0400
> Daniel Jacobowitz <drow@false.org> wrote:
>
> > What do you think, Kevin especially? I'm not entirely thrilled with
> > the way this interacts with other solib_ops vectors, but I'm not
> > unhappy with it either.
>
> What in particular were you not thrilled with?
I had to add two new methods, add_one_library and remove_one_library,
that don't make sense for any of the other things using solib_ops.
I thought for a bit about making this something completely different,
so that you could have both a solib_ops and target-reported libraries;
I think we'll want multiple sorts of libraries someday, but today
I couldn't make it work sensibly.
Also, the in_dynsym_code method is a bit hokey; calling in_plt_section
happens to be right for SymbianOS, but I have a feeling Windows will
want something more (at least, the relevant test is gdb1555.exp, and
it fails on Windows once I add testsuite support to run it there).
I suspect this should be split into a solib_ops specific bit and an
architecture specific bit, or maybe just an architecture specific bit.
Neither of these are big problems, really.
> I've looked over the solib-specific changes. They look reasonable to
> me. I didn't understand the infrun changes. I too would like to see
> that put into a different patch.
Coming right up (well, probably Monday at this point). Test case for
it, too.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-05-11 18:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 20:16 Daniel Jacobowitz
2007-05-10 3:18 ` Eli Zaretskii
2007-05-11 17:24 ` Daniel Jacobowitz
2007-05-11 17:39 ` Eli Zaretskii
2007-05-10 21:35 ` Mark Kettenis
2007-05-11 3:35 ` Daniel Jacobowitz
2007-05-15 13:28 ` Daniel Jacobowitz
2007-05-21 12:00 ` Daniel Jacobowitz
2007-07-02 21:37 ` Daniel Jacobowitz
2007-05-11 18:02 ` Kevin Buettner
2007-05-11 18:21 ` Daniel Jacobowitz [this message]
2007-05-11 23:31 ` Pedro Alves
2007-05-16 22:59 ` Jim Blandy
2007-05-18 0:27 ` Daniel Jacobowitz
2007-05-18 16:04 ` Jim Blandy
2007-05-18 16:10 ` Daniel Jacobowitz
2007-05-18 16:49 ` Jim Blandy
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=20070511182103.GA2500@caradoc.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