public inbox for
 help / color / mirror / Atom feed
From: Andrew Cagney <>
To: Elena Zannoni <>
Cc: frysk <>
Subject: Re: C++ debugger mailing list
Date: Tue, 08 Jul 2008 13:40:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Elena Zannoni wrote:
> Andrew Cagney wrote:
>> I'd like to propose that discussions and planning for this new 
>> project (or rebooted frysk as some have called it) be on a dedicated 
>> mailing list (it can be bootstrapped using frysk's membership), and 
>> then we extend a hand to gdb@ developers inviting them to participate.
>> I think an invitation to interested gdb developers to something 
>> clearly not frysk and not gdb, would be a strong symbolic gesture to 
>> all concerned that the intent here is inclusion.
>> Andrew
> Can somebody elaborate?
> We'd like to participate in these ongoing discussions for the new 
> project, whatever that is.

The goal of the frysk project is to implement an allways on monitoring 
and debugging tool, with key focus points being visual or graphical 
interface, non-stop and saleability.  And in particular, to not just 
re-implement GDB.  This drove decisions such as language choice and 
architecture, directions and goals, and also the decision to start with 
a relatively clean slate.

Red Hat have decided to withdraw their support for the frysk project and 
its goals, and are now instead focusing their efforts on a more clearly 
and narrowly defined goal of implement the Best C++ debugger, and in 
C++.  Tom is leading this new effort.

This of course leads us to a number of questions that I'm sure you're 
too familiar with (having struggled with them at the start of the frysk 
-> do you start a new community around a new code base
-> do you fork an existing community and code base; GDB or frysk
-> do you work with an existing community, in particular GDB

A lot has changed over the last few years; for instance GOLD; GCC moving 
to C++; and GDB's increased level of activity and functionality.   An 
evaluation of the above in light of this new environment, is important.

Finally, a mistake I must recognize with frysk was not trying to engage 
the GDB community, and I look forward to seeing that mistake redressed 
with this new effort; and that I guess is my motivation for proposing a 
neutral discussion ground.   Shall we set something up, gdb++ frysk++ ...?

      parent reply	other threads:[~2008-07-08 13:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04 20:32 Andrew Cagney
2008-07-07 18:55 ` Elena Zannoni
2008-07-07 20:08   ` Tom Tromey
2008-07-08 13:40   ` Andrew Cagney [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).