Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@red-bean.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org
Subject: Re: [RFC] plugin/extension interface
Date: Fri, 02 Dec 2005 23:07:00 -0000	[thread overview]
Message-ID: <8f2776cb0512021507m52b9d491gd4ddc0ceaab594ba@mail.gmail.com> (raw)
In-Reply-To: <200512022241.jB2Mf3Fk024314@elgar.sibelius.xs4all.nl>

On 12/2/05, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> I really doubt that.  Short term it'd only increase the load since we
> have to build the plug-in interface.  Long term, we still have to
> maintain that interface.  We'll also get lots of support questions
> where the problems are really with the third party plugins, but where
> the bug reporter conveniently forgets to mention that he's using a
> third party plugin.  Let's keep people out of our address space if
> they don't want to commit themselves to providing sources and manpower
> to maintain those sources.

I don't think you're seeing the potential here.  There are a *lot* of
things people would like to do with debuggers: it's one of the best
fields for productive creeping featurism you can imagine.  Writ broad,
a debugger is a program for watching your program run.  That's open to
so much application-specific interpretation it's actually hard to
imagine how generic code (like GDB) would even be useful, if you
haven't seen it in action.

In other words, if the plug-ins had enough hooks to customize GDB's
behavior (printing values, or decoding the stack, say), I think you'd
be really surprised what people would do with it.  They'd do tons of
stuff that we'd never want to include in the core distribution, but
which would add enormous value to GDB for their problems.  And of
course, there would be a few that we'd want to incorporate.

To take another tack: plug-ins were vital to Apache's success.  Why
wouldn't they have the same effect on GDB?

The only qualification I'd make here is that GDB's current internal
organization isn't very friendly to this kind of stuff.  A plug-in
interface that could engender the kind of stuff I'm describing would
have to be pretty clean, high-level, and documented.  I could
certainly see the argument that it's too much work to bring things to
the point where they could bring about the benefits.

... Okay, another qualification is that a well-integrated scripting
language might do everything I'm saying here, and better, because the
extension/core interface is more well-defined.


  reply	other threads:[~2005-12-02 23:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 18:25 Andrew STUBBS
2005-12-02 18:49 ` Eli Zaretskii
2005-12-02 19:23   ` Daniel Jacobowitz
2005-12-02 19:36 ` Mark Kettenis
2005-12-02 22:12   ` Jim Blandy
2005-12-02 22:16     ` Daniel Jacobowitz
2005-12-02 22:41     ` Mark Kettenis
2005-12-02 23:07       ` Jim Blandy [this message]
2005-12-02 23:13         ` Bob Rossi
2005-12-02 23:32         ` Daniel Jacobowitz
2005-12-03  0:57           ` Jim Blandy
2005-12-03  2:32             ` Daniel Jacobowitz
2005-12-03  2:41               ` Russell Shaw
2005-12-03  2:45                 ` Daniel Jacobowitz
2005-12-03  3:13                   ` Russell Shaw
2005-12-03  3:33                     ` Daniel Jacobowitz
2005-12-03  4:05                       ` Russell Shaw
2005-12-03  4:14                         ` Daniel Jacobowitz
2005-12-03  4:44                           ` Russell Shaw
2005-12-03  4:49                             ` Daniel Jacobowitz
2005-12-03  5:25                               ` Russell Shaw
2005-12-03 12:49                                 ` [commit] Clarify "monitor" command (was: [RFC] plugin/extension interface) Eli Zaretskii
2005-12-03 12:51                                   ` [commit] Clarify "monitor" command Russell Shaw
2005-12-03 16:08                                   ` [commit] Clarify "monitor" command (was: [RFC] plugin/extension interface) Daniel Jacobowitz
2005-12-03  5:06                             ` [RFC] plugin/extension interface Russell Shaw
2005-12-03  5:12                               ` Daniel Jacobowitz
2005-12-03  9:29                             ` Eli Zaretskii
2005-12-03  9:50                               ` Russell Shaw
2005-12-03  9:57                                 ` Eli Zaretskii
2005-12-03  2:41               ` Bob Rossi
2005-12-05 16:17 ` Andrew STUBBS
2005-12-05 16:34   ` Bob Rossi

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=8f2776cb0512021507m52b9d491gd4ddc0ceaab594ba@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=gdb@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