From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Frysk List <frysk@sourceware.org>
Subject: Re: Roadmap beginnings
Date: Mon, 14 Jul 2008 16:45:00 -0000 [thread overview]
Message-ID: <20080714164531.GA6283@caradoc.them.org> (raw)
In-Reply-To: <m3hcas8lxv.fsf@fleche.redhat.com>
On Mon, Jul 14, 2008 at 10:33:48AM -0600, Tom Tromey wrote:
> Thanks in particular for your comments on the particular C++ work
> items. I think those combined form a pretty powerful argument.
> There's still some unaddressed though:
>
> * Multi-process. I've seen some hints on the list that this is
> coming, but not enough info to really understand. This seems like
> something that would affect many areas -- there would seem to be
> challenges from the CLI on down.
Yes. I can say that CodeSourcery is working on this, and I fully
expect to have an implementation posted by ... say ... mid-October.
Focus is likely to be on MI, though it will certainly be somehow
CLI-accessible. We plan to do the work (or at least the design) in
public; if anyone wants to help...
> * Scalability to lots of shared libraries. This is tied into the
> above.
I have some general thoughts about this, but nothing concrete.
> Dodji sent me some interesting links to totalview docs. They do seem
> to have a lot of additional core functionality -- process-group stuff
> similar to what HPD specifies, the ability to evaluate C/Fortran/asm
> code fragments (nice!), memory debugging (overflows, bad free calls,
> etc), tracepoints.
One thing that might benefit GDB is for someone to sit down and come
up with a few new-approach-to-debugging features like these. Stick
them up on the wiki or something...
A nice thing about new features is that they're shiny, a.k.a. a good
draw-in for new contributors.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-07-14 16:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 19:53 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 [this message]
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 ` Debugger Work (Was: Roadmap beginnings) Tom Tromey
2008-07-11 22:48 ` Roadmap beginnings Phil Muldoon
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=20080714164531.GA6283@caradoc.them.org \
--to=drow@false.org \
--cc=frysk@sourceware.org \
--cc=tromey@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).