From: Steven Johnson <sjohnson@neurizon.net>
To: Stan Shebs <shebs@apple.com>
Cc: Andrew Cagney <ac131313@cygnus.com>,
Quality Quorum <qqi@world.std.com>,
gdb@sources.redhat.com
Subject: Re: gpl, gdb and wigglers.dll
Date: Mon, 07 May 2001 18:05:00 -0000 [thread overview]
Message-ID: <3AF80B62.98C2B97B@neurizon.net> (raw)
In-Reply-To: <3AF71F8F.8C15E1B2@apple.com>
Stan Shebs wrote:
>
> Andrew Cagney wrote:
> >
> > [...] should GDB
> > even include the source to code that allows it to use proprietary debug
> > interfaces?
[snip]
>
> I don't believe this practice violates the letter of the GPL, but
> it is in a gray area.
[snip]
> So as a matter of principle, it would be better to remove ser-ocd.c
> from the sources and explain why. Perhaps the official deprecation
> will encourage someone to work up some free source that will work
> with a wiggler, much as was done for m68k bdm years ago (though never
> incorporated into GDB, sigh).
>
I agree with all of this, if a vendor wishes to include proprietary
interfaces
to closed source DLL's they can:
1. Have patches available on their web site for the interface.
2. Build a server program that communicates to GDB using the GDB remote
serial protocol (and therefore does not require any pathces to GDB)
3. Release the communication details of the device so that the DLL can
be used on windows, but other direct alternatives can be provided for
other platforms.
This always seemed against the spirit of the GPL to me.
BTW. I don't think ser-ocd.c is the only file that does this, I seem to
remember one other interface as well.
Steven Johnson
next prev parent reply other threads:[~2001-05-07 18:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 12:34 Quality Quorum
2001-05-07 13:20 ` Andrew Cagney
2001-05-07 13:42 ` Quality Quorum
2001-05-07 15:21 ` Stan Shebs
2001-05-07 18:05 ` Steven Johnson [this message]
2001-05-08 7:03 ` Quality Quorum
2001-05-08 11:20 ` Tom Tromey
2001-05-09 0:18 ` Baurjan Ismagulov
2001-05-09 8:59 ` DJ Delorie
2001-05-09 10:16 ` Tom Tromey
2001-05-09 12:41 ` Stan Shebs
2001-05-09 13:15 ` DJ Delorie
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=3AF80B62.98C2B97B@neurizon.net \
--to=sjohnson@neurizon.net \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=qqi@world.std.com \
--cc=shebs@apple.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