From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 6
Date: Fri, 09 May 2003 20:25:00 -0000 [thread overview]
Message-ID: <3EBC0EB6.4050201@redhat.com> (raw)
In-Reply-To: <200305091817.h49IHiYN011921@duracef.shout.net>
> Andrew Cagney writes:
>
>> Given this, I think the next release of GDB should be named ``GDB 6''.
>
>
> I was hoping that it would be gdb 5.4, and that we would tell
> everyone that has 5.3 that it's good for them to upgrade to 5.4.
>
> Guess I'm outvoted. :)
It's all marketing anyway :-)
> The last time I compared 5.3 to HEAD was more than a month ago.
> HEAD was in pretty good shape then -- better than gdb-5_3-branch
> was when it was branched.
>
> I will try to get back to testing and reporting soon, but I can't
> promise anything.
Mostly yes.
[poor] Kevin keeps finding problems with with the MIPS and the new frame
code. I'd suspect a similar situtation with other architectures. So
when it works it works well, but when it fails it really goes down -
typical behavior for a new .0 release :-^
Andrew
next prev parent reply other threads:[~2003-05-09 20:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 18:17 Michael Elizabeth Chastain
2003-05-09 20:25 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
2003-05-09 20:21 ` Andrew Cagney
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=3EBC0EB6.4050201@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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).