Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@apple.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Quality Quorum <qqi@world.std.com>, gdb@sources.redhat.com
Subject: Re: gpl, gdb and wigglers.dll
Date: Mon, 07 May 2001 15:21:00 -0000	[thread overview]
Message-ID: <3AF71F8F.8C15E1B2@apple.com> (raw)
In-Reply-To: <3AF7038A.9080908@cygnus.com>

Andrew Cagney wrote:
> 
> [...] should GDB
> even include the source to code that allows it to use proprietary debug
> interfaces?  I'm guessing, but I suspect that the current pratice has
> been that such code should be included as it makes GDB accessible to a
> wider set of users.  At the same time, however, it also precluding the
> possibility of a dll vendor directly benefiting by distributing a GDB
> binary.

I don't believe this practice violates the letter of the GPL, but
it is in a gray area.  The GPL says source code need not "include
anything that is normally distributed with [...] the operating
system".  The wiggler dll is basically a driver for an addon piece
of hardware, so one could argue that it is a normal component of the
operating system for a PC+wiggler combination.  In that respect it
would be no different from having, say, an XFree86 that includes a
special hack to use a Windows-binary-only 3D card driver, even when
running on GNU/Linux.

However, in retrospect, I made a mistake in deciding to include
ser-ocd.c.  The problem is that with an unspecified interface
between PC and wiggler, and with the wiggler dll only available in
binary form for certain platforms (correct me if I'm wrong here),
you have the situation that the GPL was supposed to prevent, namely
that you can't fix a problem in the driver, use it with a different
operating system, etc.  For instance, if I get a Mac with a parallel
port, I can't use the wiggler I already bought, no matter whether I run
LinuxPPC or OS X.  Even a minor Linux or Windows upgrade could render
my wiggler useless.

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).

Stan


  parent reply	other threads:[~2001-05-07 15:21 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 [this message]
2001-05-07 18:05     ` Steven Johnson
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=3AF71F8F.8C15E1B2@apple.com \
    --to=shebs@apple.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=qqi@world.std.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