Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc / remote protocol] Remote shared library events
Date: Fri, 11 May 2007 03:35:00 -0000	[thread overview]
Message-ID: <20070511033500.GE3187@caradoc.them.org> (raw)
In-Reply-To: <200705102134.l4ALYpQU016401@brahms.sibelius.xs4all.nl>

On Thu, May 10, 2007 at 11:34:51PM +0200, Mark Kettenis wrote:
> > Date: Wed, 9 May 2007 16:16:27 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> > 
> > Not all platforms work this way.  The exceptions I'm looking at
> > recently are DLL-based platforms: Windows and SymbianOS.  Both use an
> > OS-level loader instead.  You have to query the OS to get the list
> > of libraries, and the OS provides event notification directly instead
> > of via a magic breakpoint.  We can't poke and prod at the OS directly
> > during remote debugging, so to implement DLL support for these
> > platforms I extended the remote protocol.
> 
> Can we please avoid the term DLL for this stuff?  That's just a
> particular implementation of shared objects/libraries.  This
> functionality is generally usable, and not specific to Windows.

Every platform I've used that needs the OS-provided events called them
DLLs, which was more than just Windows :-)  But I've no objection.
I'll rephrase the patch.

I'd rather leave the packet names alone, but if you would rather
change them I can keep the old names in a local patch for now.

> I think this diff needs to be split up.  I looked at it twice now, but
> I don't see how the bits are related, and the changes to infrun.c make
> me very nervous.

I can definitely split out the infrun bits; I'll do that tomorrow and
post them with their own explanation.  If there's anything else that
you would like split out or clarified, let me know.  Better overall
explanation of solib-target coming up too.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-05-11  3:35 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 [this message]
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
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=20070511033500.GE3187@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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