From: Bob Rossi <bob@brasko.net>
To: Jim Blandy <jimb@red-bean.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb@sourceware.org
Subject: Re: [RFC] plugin/extension interface
Date: Fri, 02 Dec 2005 23:13:00 -0000 [thread overview]
Message-ID: <20051202231302.GA10388@white> (raw)
In-Reply-To: <8f2776cb0512021507m52b9d491gd4ddc0ceaab594ba@mail.gmail.com>
On Fri, Dec 02, 2005 at 03:07:29PM -0800, Jim Blandy wrote:
> 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.
>
> 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.
I'm already in the long process of creating a level on top of GDB using
MI that allows another process to do anything it wants with GDB. IMO,
that is already the clean, high-level, documented interface that other
applications should use to communicate with GDB.
If the interface needs to change, that's where the effort should go. I
don't think providing any other plugin interface besides what's
described above even makes sense since it would be duplicating the
effort.
Bob Rossi
next prev parent reply other threads:[~2005-12-02 23:13 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
2005-12-02 23:13 ` Bob Rossi [this message]
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 ` Bob Rossi
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-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=20051202231302.GA10388@white \
--to=bob@brasko.net \
--cc=gdb@sourceware.org \
--cc=jimb@red-bean.com \
--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