From: Per Bothner <per@bothner.com>
To: Quality Quorum <qqi@world.std.com>
Cc: GDB Discussion <gdb@sources.redhat.com>
Subject: Re: Where is GDB going
Date: Mon, 26 Feb 2001 13:45:00 -0000 [thread overview]
Message-ID: <m2elwl2jq3.fsf@kelso.bothner.com> (raw)
In-Reply-To: <Pine.SGI.4.21.0102261222390.8709-100000@world.std.com>
Quality Quorum <qqi@world.std.com> writes:
> If GNU is going to become a social engineering tool ..
It has been, since it was launched in 1984. Check www.gnu.org.
> It was you idea to discuss this matter under this angle.
No, you were whining that the GPL 3.0 might be preventing you
from using Gdb, and complaining this would be wrong.
> I had
> a very simple question I would like to be either firmly confirmed or
> firmly denied. If I have i386-stub.c (which is public domain) linked with
> my evil-proprietary-system then it will be breach of GPL 3.0 to debug
> my evil-proprietary-system with GDB using GDB remote protocol.
This cannot be confirmed, since GPL 3.0 does not exist.
I would not worry about GPL 3.0. It is a hypothetical problem. Your
concern should be whether GPL 2.0 allows you to do what you need to
do; I believe it does. If a future GPL 3.0 is too restrictive, you
always have the option of sticking with an older version of Gdb.
The GPL does allow you to create your own fork, if you want to,
from say Gdb 5.0.
--
--Per Bothner
per@bothner.com http://www.bothner.com/~per/
next prev parent reply other threads:[~2001-02-26 13:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 13:52 Andrew Cagney
2001-02-23 14:21 ` Quality Quorum
2001-02-25 15:48 ` Steven Johnson
2001-02-25 21:15 ` Quality Quorum
2001-02-25 23:41 ` Per Bothner
2001-02-26 9:39 ` Quality Quorum
2001-02-26 10:02 ` correction. " Quality Quorum
2001-02-26 13:45 ` Per Bothner [this message]
2001-02-26 16:29 ` Quality Quorum
2001-02-26 13:53 ` Steven Johnson
2001-02-25 18:11 Peter Reilley
2001-02-25 20:52 ` Steven Johnson
2001-02-25 21:22 ` Quality Quorum
2001-02-26 20:34 Peter Reilley
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=m2elwl2jq3.fsf@kelso.bothner.com \
--to=per@bothner.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).