public inbox for rda@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Pierre Muller <muller@cerbere.u-strasbg.fr>,
	rda@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: [ADMINISTRIVIA] New RDA mailing list
Date: Sun, 01 Dec 2002 15:19:00 -0000	[thread overview]
Message-ID: <20021201231925.GA16409@nevyn.them.org> (raw)
In-Reply-To: <3DEA91A9.6010009@redhat.com>

On Sun, Dec 01, 2002 at 05:48:09PM -0500, Andrew Cagney wrote:
> 
> >>No.  GDBSERVER is part of GDB (which is part of the FSF's GNU project) 
> >>and it should continue to be discussed here.
> >
> >
> >I really wish we could come to some resolution about the overlap. 
> >Should we sacrifice the FSF-owned gdbserver project in favor of
> >extending RDA?  As it is, there's a substantial amount of duplicated
> >effort.  I hate seeing effort wasted.
> 
> gdb/gdbserver/ is the FSF's (and hence GDB's) remote debug agent.  There 
> is no benefit to the FSF, and its objectives, in replacing something (C) 
> FSF with something (C) Red Hat.

There is no benefit to the community in having a publicly developed RDA
that I can see.  Right now I don't believe it has any features that
gdbserver doesn't, although I could be wrong - I only checked briefly -
I know that it used to have threads support when gdbserver didn't but
we implemented that before RDA was released.

And now Red Hat employees can contribute things like tracepoint support
to the community by adding them to the (c) Red Hat RDA, when the
community would benefit as much or more having them in gdbserver.  So
we get two stubs with mostly-overlapping but different feature sets.

Obviously Red Hat doesn't want to drop RDA in favor of gdbserver.  But
having gdbserver as a second-rate cousin until someone spends weeks
playing feature catchup with RDA (e.g. I or someone else finds the time
to implement the introspect stuff in gdbserver, if I can even do it...)
does no one but Red Hat any good.

I'm sorry to keep harping on this unpleasant subject, but it really
irks me.  There's a gdbserver project out there to contribute to.  It
was in bad shape; I like to think we've put it back together now!

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2002-12-01 23:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021127034054.GA1477@redhat.com>
2002-11-26 19:46 ` Christopher Faylor
2002-11-27  1:00 ` Pierre Muller
2002-11-27  7:18   ` Andrew Cagney
2002-12-01 13:21     ` Daniel Jacobowitz
2002-12-01 14:50       ` Andrew Cagney
2002-12-01 15:19         ` Daniel Jacobowitz [this message]
     [not found]           ` <mailpost.1038784758.15335@news-sj1-1>
2002-12-02 12:02             ` Chris G. Demetriou

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=20021201231925.GA16409@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=muller@cerbere.u-strasbg.fr \
    --cc=rda@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).