From: Steven Johnson <sjohnson@neurizon.net>
To: gdb@sources.redhat.com
Subject: Re: GDB is the GNU project's native debugger
Date: Wed, 17 Nov 2004 00:31:00 -0000 [thread overview]
Message-ID: <419A943B.7020106@neurizon.net> (raw)
In-Reply-To: <419A2E2F.5010602@gnu.org>
Andrew Cagney wrote:
> 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?
>
>
My 2c.
The statement doesnt mean anything.
As the code in GDB is developed by the donations of people, in either
time or money to companies who spend time. The "primary" focus of GDB
will always be the focus of the majority of "donators/contributors" at
any one time, and will change over time, as the groups "majority" need
changes.
The (flavour of Open Source) licence is largely irrelevent, except to
the point that it allows people to feel (more or less) comfortable in
donating their time to a "common good".
So no, i dont agree with this statement.
I would agree with a statement that said "the majority of people (at the
current time) who use GDB are debugging programs compiled with GCC".
After that, if tomorrow we get 1000 developers donating their time to
support Windows XP native debugging of Visual C++, thats going to be the
"priority" because they will swamp (by their needs and the level of
their donation at the current time) the needs and level of donation of
all others combined. And we as a group should be thankful for that,
because it is unlikely that all that work will only be useful for one
target platform, so even if it doesnt advance the philosophical war, it
certainly advances the tool which we all use.
Andrew, Can you illuminate us as to why this "philosophical" debat has
been raised? What problem are you trying to solve or prevent?
My belief is one of the pleasures of the GDB community is the lack of
this sort of largely pointless debate.
Steven
next prev parent reply other threads:[~2004-11-16 23:58 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
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 [this message]
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=419A943B.7020106@neurizon.net \
--to=sjohnson@neurizon.net \
--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