public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Bob Rossi <bob_rossi@cox.net>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 6
Date: Fri, 09 May 2003 18:05:00 -0000	[thread overview]
Message-ID: <20030509180511.GA12861@white> (raw)
In-Reply-To: <3EBBDE20.6030007@redhat.com>

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.  

What exactly do you mean here?
Annotations Level 2 will stay in gdb for version 6.0?
This would truly be a great thing.

Bob Rossi

  parent reply	other threads:[~2003-05-09 18:05 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
2003-05-09 18:05 ` Bob Rossi [this message]
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=20030509180511.GA12861@white \
    --to=bob_rossi@cox.net \
    --cc=ac131313@redhat.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).