From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 6.2 release schedule?
Date: Fri, 18 Jun 2004 15:33:00 -0000 [thread overview]
Message-ID: <40D30B2B.6090609@gnu.org> (raw)
In-Reply-To: <20040617210340.367834B104@berman.michael-chastain.com>
> I think July 1 is too soon to cut the branch.
>
> native i686-pc-linux-gnu has two regressions from gdb 6.1 to gdb HEAD.
>
> gdb/1650 manythreads.exp
> gdb/1677 [regression] selftest.exp, crash in lookup_symtab
>
> 1677 is probably easy to fix. 1650 looks significantly deeper.
> The problem with 1650 is that gdb HEAD randomly gets internal errors,
> but gdb 6.1 does not, on the same test script.
These worry me (btw, no one got around to moving selftest.exp to
testsuite/gdb.gdb/ :-).
> native hppa2.0w-hp-hpux11.11 has regressions in 17 test scripts.
> I estimate there's about 1 real regression bug per 4-5 test scripts,
> so there are about 4-5 real regression bugs to hunt down and fix
> (or document).
>
> http://sources.redhat.com/ml/gdb-testers/2004-q2/msg00160.html
> http://sources.redhat.com/ml/gdb-testers/2004-q2/msg00157.html
But these don't. Presumably being ISA specific its possible to have
fixes easily pulled into the branch.
There's also a balancing act here. GDB as a whole should continue to
improve. While there are the above regressioins, there are also
dramatic improvements on other ISAs such as i386 and PPC/PPC64.
enjoy,
Andrew
next prev parent reply other threads:[~2004-06-18 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 21:03 Michael Elizabeth Chastain
2004-06-18 15:33 ` Andrew Cagney [this message]
2004-06-29 14:28 ` Randolph Chung
-- strict thread matches above, loose matches on Subject: below --
2004-06-18 15:43 Michael Elizabeth Chastain
2004-06-18 17:02 ` Andrew Cagney
2004-06-17 20:32 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=40D30B2B.6090609@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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