From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Discussion <gdb@sources.redhat.com>
Subject: Where is GDB going
Date: Fri, 23 Feb 2001 13:52:00 -0000 [thread overview]
Message-ID: <3A96DB35.69A12FC8@cygnus.com> (raw)
Just FYI,
I'm currently aware of three significant and ongoing architectural
developments in GDB (I use the word `ongoing' loosely as like any work
it suffer from fits and starts):
o mi/libgdb/cli
An interface for building better
and more robust GUIs. If is signficant
as it involves separating the CLI
from the core of GDB.
o multi-arch
Allowing GDB to debug more complex
targets containing several architectures
o async/event-loop
Eliminating the assumption that
the world stops when the target
Beyond that I also know of some more localized development (C++
cleanup/revamp, harvard/segment architecture discussion, ...).
Andrew
next reply other threads:[~2001-02-23 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 13:52 Andrew Cagney [this message]
2001-02-23 14:21 ` Quality Quorum
2001-02-25 15:48 ` Steven Johnson
2001-02-25 21:15 ` Quality Quorum
2001-02-25 23:41 ` Per Bothner
2001-02-26 9:39 ` Quality Quorum
2001-02-26 10:02 ` correction. " Quality Quorum
2001-02-26 13:45 ` Per Bothner
2001-02-26 16:29 ` Quality Quorum
2001-02-26 13:53 ` Steven Johnson
2001-02-25 18:11 Peter Reilley
2001-02-25 20:52 ` Steven Johnson
2001-02-25 21:22 ` Quality Quorum
2001-02-26 20:34 Peter Reilley
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=3A96DB35.69A12FC8@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@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).