From: Jelmer Vernooij <jelmer@samba.org>
To: Scott Moser <ssmoser@us.ibm.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] plugin patch
Date: Wed, 06 Nov 2002 06:56:00 -0000 [thread overview]
Message-ID: <20021106145415.GA2350@charis.vernstok> (raw)
In-Reply-To: <Pine.LNX.4.44.0211060843060.18844-100000@dmfet>
On Wed, Nov 06, 2002 at 08:45:18AM -0600, Scott Moser wrote about 'Re: [PATCH] plugin patch':
> All,
> I sent a patch to add plugin support to GDB under this subject last
> week, and hadn't received a response other than the one below.
> I'll gladly document the plugin in gdbint.texinfo if needed. IBM
> made a copyright assignment agreement previously and I have the required
> papers to assign this patch also.
> I don't think that beneficial functionality should be kept from gdb
> simply because people might use it in unfriendly ways. Anyone
> interested in taking gdb functionality could still get the GDB source
> and highjack that (which would even be less obvious to detect than
> shipping a file and telling the user to "plugin load" it within GDB).
> If my patch was submitted incorrectly, there was something else
> that I was missing, or anything else I'd need to change/update/add,
> please let me know.
One small suggestion; add some kind of version system for the plugins.
The API for plugins might change in the future and you don't want bug
reports from users complaining that gdb segfaults when they're trying
to load a plugin. We had the same thing when implementing this in
samba.
Just my two eurocents, :-)
jelmer
> On Tue, 29 Oct 2002, Eli Zaretskii wrote:
> > On Mon, 28 Oct 2002, Scott Moser wrote:
> > > Below is a patch to add plugin support to GDB. It exports a fairly
> > > simple programmable interface for people to extend the functionality of
> > > GDB via runtime loaded shared libraries in ways that may not fit with
> > > the direction of the main GDB tree (not cross-platform, not stable,
> > > niche audience...).
> > IIRC, the FSF doesn't like to add to GNU software support for dynamically
> > loading arbitrary modules (for fear of non-free libraries being used thru
> > this).
> > In any case, if this is approved, please consider documenting it in
> > gdbint.texinfo. TIA
> Scott Moser
> Software Engineer; Linux Technology Center
> IBM Corp., Austin, Tx
> (512) 838-1533 T/L: 678-1533
> ssmoser@us.ibm.com , internal zip: 9812
--
Jelmer Vernooij <jelmer@nl.linux.org> - http://nl.linux.org/~jelmer/
15:51:44 up 3:40, 9 users, load average: 0.11, 0.10, 0.08
next prev parent reply other threads:[~2002-11-06 14:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 14:01 Scott Moser
2002-10-28 22:28 ` Eli Zaretskii
2002-10-29 7:55 ` Paul A. Clarke
2002-11-06 6:45 ` Scott Moser
2002-11-06 6:56 ` Jelmer Vernooij [this message]
2002-11-06 7:13 ` Scott Moser
2002-11-06 7:54 ` Jelmer Vernooij
2002-11-06 9:14 ` Andrew Cagney
2002-11-06 15:07 ` Paul A. Clarke
2002-11-06 15:56 ` Andrew Cagney
2002-11-07 10:05 ` Paul A. Clarke
2002-11-07 11:57 ` Andrew Cagney
2002-11-07 13:10 ` Klee Dienes
2002-11-06 15:56 ` Andrew Cagney
2002-11-06 7:47 Howell, David P
2002-11-06 7:55 ` Daniel Jacobowitz
2002-11-06 11:12 ` Andrew Cagney
2002-11-06 11:55 ` Paul A. Clarke
2002-11-06 12:29 ` 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=20021106145415.GA2350@charis.vernstok \
--to=jelmer@samba.org \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=ssmoser@us.ibm.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