public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 6
Date: Fri, 09 May 2003 17:41:00 -0000	[thread overview]
Message-ID: <16059.59758.609479.734628@localhost.redhat.com> (raw)
In-Reply-To: <20030509171224.GA15350@nevyn.them.org>

Daniel Jacobowitz writes:
 > On Fri, May 09, 2003 at 12:58:08PM -0400, Andrew Cagney wrote:
 > > The sole objective for GDB 6 was to have GDB multi-arch.  Since Joel has 
 > > now committed a change that multi-arch partial's the HP/PA, and all 
 > > architectures can be built multi-arch partial, it can be argued that GDB 
 > > has technically reached this goal(1).
 > > 
 > > Given this, I think the next release of GDB should be named ``GDB 6''.
 > > 
 > > In doing this, there is an oportunity to, identify as obsolete (but not 
 > > actually delete) a few extra bits..  The following come to mind:
 > > 
 > > - non event loop platforms
 > > - DWARF (a.k.a., DWARF 1)
 > > 
 > > People with systems that rely on said features can always download the 
 > > GDB 5 series debuggers.
 > > 
 > > With regard to annotations, someone [me] still still has the 
 > > documentation and testsuite to update (....).  That, I think is the only 
 > > ``must have'' thing for the next GDB release.  Other things such as NPTL 
 > > et.al. are obvious nice to have (and probably will because more people 
 > > are motivated to get them in :-).
 > > 
 > > Andrew
 > > 
 > > (1) Just ignore the cleanup that will eventually follow, oh and that one 
 > > of the SPARC and HP/PA variants still need some work.
 > 
 > It sounds mighty good to me.
 > 
 > I'd like to see the new dwarf-frame code finished before GDB 6, but it
 > sounds like we'll have (just?) enough time.
 > 

me too! me too!
I think we'll also have objc finished (there is only one last patch pending).
I'll go after DavidC patches for namespaces now....

there are so many new things that we could bump the version number up to 7!

elena


 > -- 
 > Daniel Jacobowitz
 > MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-05-09 17:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09 16:58 Andrew Cagney
2003-05-09 17:12 ` Daniel Jacobowitz
2003-05-09 17:41   ` Elena Zannoni [this message]
2003-05-09 18:05 ` Bob Rossi
2003-05-09 20:21   ` Andrew Cagney
2003-05-09 18:17 Michael Elizabeth Chastain
2003-05-09 20:25 ` Andrew Cagney
2003-05-10 22:35 Nick Roberts
2003-05-11 15:22 ` Andrew Cagney
2003-05-12 18:57   ` Nick Roberts
2003-05-11 22:00     ` Andrew Cagney
2003-05-12 19:29     ` Bob Rossi
2003-05-13 17:47       ` Nick Roberts
2003-05-12 19:36     ` Bob Rossi
2003-05-13 17:47       ` Nick Roberts

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=16059.59758.609479.734628@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=drow@mvista.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).