From: "Dave Korn" <dk@artimi.com>
To: "'Andrew Cagney'" <cagney@gnu.org>, <gdb@sources.redhat.com>
Subject: RE: GDB is the GNU project's native debugger
Date: Tue, 16 Nov 2004 18:11:00 -0000 [thread overview]
Message-ID: <NUTMEGIOFByastN5m7m000007c5@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <419A2E2F.5010602@gnu.org>
> -----Original Message-----
> From: gdb-owner On Behalf Of Andrew Cagney
> Sent: 16 November 2004 16:43
> GDB is the GNU project's native debuger. While we're
> certainly happy to
> accomodate people using GDB as either an embedded debugger or native
> debugger on other systems, the need to persue GDB as a native
> debugger
> on GNU systems must be our first priority.
>
> Do we all agree with this?
Well, "Up to a point, Lord Copper".
I will take it that you do not mean that the primary purpose of GDB is to run
under the HURD, since that doesn't really fully exist or work. I'm not sure
what you mean by "GNU system**S**" in the plural, because that's the only one.
Unixen are largely proprietary, and GNU/Linux is GNU/Linux, and not just plain
GNU. If you'd care to enlarge and clarify on the precise shade of meaning you
were attaching to the phrase, I might modify some of what follows from here.
To my understanding, and correct me if you feel I've misunderstood, a major
part of the purpose of the GNU project is to encourage and evangelise the spread
of open source, and the strategic method for achieving that goal is to provide
free software, in particular a free toolchain, across as wide a range of
platforms as possible, and in particular the reason for the existence of the
LGPL exception is to enable the GNU toolchain and software family to be ported
to proprietary systems and to make inroads for open software there and convince
users of proprietary systems of the value and benefits that can be obtained from
the open source philosophy.
So while I can see that it would make both philosophical, technical and
political sense to prioritise support for the more open systems above support
for proprietary ones, I don't think that policy should be pursued
over-zealously. We _want_ users of proprietary systems to throw away their
proprietary tools and start using open ones and writing open code.
Gcc and binutils both make a point of attempting to natively support a very
wide range of platforms for just this reason. I think that GDB should be
attempting to target fairly much the same range.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2004-11-16 17:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 17:14 Andrew Cagney
2004-11-16 17:26 ` Paul Breed
2004-11-16 17:35 ` Kris Warkentin
2004-11-16 20:09 ` Mark Kettenis
2004-11-16 17:50 ` Ian Lance Taylor
2004-11-16 21:48 ` Eli Zaretskii
2004-11-17 1:24 ` Andrew Cagney
2004-11-17 1:53 ` Ian Lance Taylor
2004-11-17 22:59 ` Andrew Cagney
2004-11-19 5:05 ` Ian Lance Taylor
2004-11-19 7:19 ` Kip Macy
2004-11-30 16:26 ` Andrew Cagney
2004-12-07 14:46 ` Ian Lance Taylor
2004-11-16 18:11 ` Dave Korn [this message]
2004-11-16 18:33 ` Ian Lance Taylor
2004-11-16 18:43 ` Dave Korn
2004-11-16 18:47 ` Ian Lance Taylor
2004-11-16 19:59 ` Mark Kettenis
2004-11-17 0:31 ` Steven Johnson
2004-11-16 19:30 Paul Schlie
2004-11-16 19:51 Paul Schlie
2004-11-16 21:11 ` Paul Breed
2004-11-16 23:58 ` Elena Zannoni
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=NUTMEGIOFByastN5m7m000007c5@NUTMEG.CAM.ARTIMI.COM \
--to=dk@artimi.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.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