Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Hooks still needed for annotations
Date: Wed, 15 Jun 2005 16:07:00 -0000	[thread overview]
Message-ID: <20050615160749.GA17626@nevyn.them.org> (raw)
In-Reply-To: <20050615155248.GC20778@white>

On Wed, Jun 15, 2005 at 11:52:48AM -0400, Bob Rossi wrote:
> > I don't much think a parser is GDB's responsibility.  Offering one as a
> > convenience, sure, maybe.  Note that a lot of frontends won't get to
> > use it anyway!  If we ship it with GDB, then it's going to be covered
> > under the GPL.
> 
> Well, could I maintain a copy under the LGPL, and then contribute all of
> the modifications to the FSF GDB under the GPL?

LGPL would not help much; you'd need something BSD-ish.  You could, of
course, do whatever you wanted to do with code that you wrote.  But I
don't think there's much point to that; if you contribute it to GDB,
that will be so that other developers can help you maintain it and keep
it up to date with changes in MI.  You won't get all the other GDB
contributors to relicense their work.

> Either way, I don't care much about commercial tools. If a good parser
> is created, I think it's possible a lot of front ends will use it. For
> instance, KGDB, DDD and GVD are all free projects that could benefit
> from such a technology. Right?

KGDB is a stub, not a frontend.  DDD could use it - not sure if
anyone's updating DDD enough nowadays to bother.  GVD could, but would
be unlikely to unless you wrote the parser in Ada!  (Not that Ada can't
use C bindings, but the GPS maintainers would presumably prefer
language consistency.)

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-06-15 16:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01  7:15 Nick Roberts
2005-06-01 11:30 ` Bob Rossi
2005-06-01 21:31   ` Nick Roberts
2005-06-03 19:09     ` Daniel Jacobowitz
2005-06-03 22:35       ` Nick Roberts
2005-06-03 23:59         ` Daniel Jacobowitz
2005-06-04  3:19           ` Nick Roberts
2005-07-03 17:03             ` Daniel Jacobowitz
2005-07-03 22:13               ` Nick Roberts
2005-07-03 22:44                 ` Daniel Jacobowitz
2005-06-04 13:02           ` Bob Rossi
2005-06-13  3:14             ` Daniel Jacobowitz
2005-06-15 15:52               ` Bob Rossi
2005-06-15 16:07                 ` Daniel Jacobowitz [this message]
2005-06-15 16:31                   ` Bob Rossi
2005-07-03 16:45                     ` Daniel Jacobowitz
2005-06-15 23:07                 ` Nick Roberts
2005-06-15 23:29                   ` Bob Rossi
2005-07-01  0:21               ` Bob Rossi
2005-07-01  1:18                 ` Nick Roberts
2005-06-06 21:57           ` Nick Roberts
2005-06-10  2:26             ` Bob Rossi
2005-06-10  3:25               ` Nick Roberts
2005-06-15 15:24                 ` Bob Rossi
2005-06-15 21:38                   ` Nick Roberts
2005-06-15 22:58                     ` Bob Rossi
2005-07-03 16:39                       ` Daniel Jacobowitz
2005-07-06 15:03                         ` Bob Rossi
2005-07-15  0:03                           ` Daniel Jacobowitz

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=20050615160749.GA17626@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@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