From: Tom Tromey <firstname.lastname@example.org>
To: Daniel Jacobowitz <email@example.com>
Cc: Frysk List <firstname.lastname@example.org>
Subject: Debugger Work (Was: Roadmap beginnings)
Date: Tue, 22 Jul 2008 20:29:00 -0000 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <20080711215243.GA30836@caradoc.them.org> (Daniel Jacobowitz's message of "Fri\, 11 Jul 2008 17\:52\:43 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <firstname.lastname@example.org> writes:
Daniel> Anyway, the trend I wanted to demonstrate: these are
Daniel> straightforward incremental additions to GDB.
Thanks for this note.
Red Hat is going to put its "best C++ debugger" efforts into gdb.
Naturally, this was not an easy decision. There are two basic reasons
that caused us to revisit gdb. One reason comes from Daniel's email:
our concrete wish-list is a series of deltas to gdb; of these some are
pretty easy, and some are difficult -- but intrinsically difficult,
not difficult due to some quirk of gdb. Another reason we took
another look at gdb is the ongoing work by Code Sourcery on non-stop
debugging and multi-process debugging.
Some folks here are worried that gdb will not satisfy Red Hat's needs
in the long term. Our plan to deal with this contingency is to
re-examine our gdb work to see how we are doing -- either at the 6
month point, or if we hit a major architectural barrier.
Our general plan is similar to what we discussed for frysk, though of
course with some changes:
* We will work on our own branch, with frequent merges from main line.
We do intend to merge things back to the trunk, but having a branch
will let us time that effort more easily. Also we want to have a
somewhat different patch review approach, so that all team members
are involved in patch review. (If you're curious, we'll most likely
use a git repository for this branch.)
* We'll set up our own mailing list(s) for discussion and patch
review. I don't mind reusing the frysk list, but YMMV... please
discuss. If you don't want the frysk list, feel free to suggest a
name for the project.
* We'll continue to discuss our roadmap and milestones in public.
This will start in earnest once the mailing list situation is clear.
* The C++ issue. We're still interested in having the debugger be
implemented in C++. However, this will probably not be the first
thing we tackle, primarily because we need various changes that will
be occurring on gdb CVS trunk.
* FWIW we're going to be looking into a couple other debugging-related
projects. In particular, in addition to Alexandre Oliva's work on
variable tracking in GCC, we will need a sub-project to change g++
to emit more debug info in some cases. Also, we'll need to work on
making gdb work with froggy (maybe on an experimental branch).
Naturally, anybody is welcome to join us in this effort.
next prev parent reply other threads:[~2008-07-22 20:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 19:53 Roadmap beginnings Tom Tromey
2008-07-11 20:56 ` Jan Kratochvil
2008-07-11 21:37 ` Tom Tromey
2008-07-11 21:54 ` Daniel Jacobowitz
2008-07-11 23:11 ` Kris Van Hees
2008-07-11 21:53 ` Daniel Jacobowitz
2008-07-14 16:34 ` Tom Tromey
2008-07-14 16:45 ` Daniel Jacobowitz
2008-07-14 16:58 ` Phil Muldoon
2008-07-14 17:09 ` Daniel Jacobowitz
2008-07-14 17:19 ` Ian Lance Taylor
2008-07-14 17:34 ` Daniel Jacobowitz
2008-07-14 18:04 ` Tom Tromey
2008-07-14 18:12 ` Daniel Jacobowitz
2008-07-14 18:11 ` Ian Lance Taylor
2008-07-14 17:35 ` Tom Tromey
2008-07-14 18:13 ` Ian Lance Taylor
2008-07-22 20:29 ` Tom Tromey [this message]
2008-07-11 22:48 ` Phil Muldoon
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).