From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Keith Seitz <keiths@redhat.com>
Subject: Re: [RFA 1/3] dwarf2_physname - cpexprs.exp
Date: Sat, 21 Nov 2009 05:21:00 -0000 [thread overview]
Message-ID: <200911210520.45772.pedro@codesourcery.com> (raw)
In-Reply-To: <4B070525.4030107@redhat.com>
On Friday 20 November 2009 21:07:49, Keith Seitz wrote:
> Running these tests on CVS HEAD currently gives (go ahead, try it: I
> dare you :-):
Oh, man,... you know one can't resist that!
> # of expected passes 77
> # of unexpected failures 54
> # of unresolved testcases 123
>
> Not good -- gdb crashes along the way.
That's what I get too.
> However, with this entire patchset applied, all 378 test in cpexprs.exp
> will pass.
FYI, with 'gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu4)' (ubuntu 8.04):
FAIL: gdb.cp/cpexprs.exp: print policyd4::policyd
FAIL: gdb.cp/cpexprs.exp: print policyd<base, operation_1<base> >::policyd
FAIL: gdb.cp/cpexprs.exp: list base::overload(base&) const
FAIL: gdb.cp/cpexprs.exp: list base::overload(char*) const
FAIL: gdb.cp/cpexprs.exp: list base::overload(int) const
FAIL: gdb.cp/cpexprs.exp: list base::overload(long) const
FAIL: gdb.cp/cpexprs.exp: list base::overload(short) const
FAIL: gdb.cp/cpexprs.exp: list base::overload(void) const
FAIL: gdb.cp/cpexprs.exp: list policyd4::policyd
FAIL: gdb.cp/cpexprs.exp: list policyd<base, operation_1<base> >::policyd
FAIL: gdb.cp/cpexprs.exp: setting breakpoint at base::overload(base&) const
FAIL: gdb.cp/cpexprs.exp: continue to base::overload(base&) const
FAIL: gdb.cp/cpexprs.exp: setting breakpoint at base::overload(char*) const
FAIL: gdb.cp/cpexprs.exp: continue to base::overload(char*) const
FAIL: gdb.cp/cpexprs.exp: setting breakpoint at base::overload(int) const
FAIL: gdb.cp/cpexprs.exp: continue to base::overload(int) const
FAIL: gdb.cp/cpexprs.exp: setting breakpoint at base::overload(long) const
FAIL: gdb.cp/cpexprs.exp: continue to base::overload(long) const
FAIL: gdb.cp/cpexprs.exp: setting breakpoint at base::overload(short) const
FAIL: gdb.cp/cpexprs.exp: continue to base::overload(short) const
FAIL: gdb.cp/cpexprs.exp: setting breakpoint at base::overload(void) const
FAIL: gdb.cp/cpexprs.exp: continue to base::overload(void) const
FAIL: gdb.cp/cpexprs.exp: setting breakpoint at policyd4::policyd
FAIL: gdb.cp/cpexprs.exp: continue to policyd4::policyd
FAIL: gdb.cp/cpexprs.exp: setting breakpoint at policyd<base, operation_1<base> >::policyd
FAIL: gdb.cp/cpexprs.exp: continue to policyd<base, operation_1<base> >::policyd
=== gdb Summary ===
# of expected passes 360
# of unexpected failures 26
/home/pedro/gdb/keithcpp/build/gdb/testsuite/../../gdb/gdb version 7.0.50.20091121-cvs -nw -nx
make[1]: *** [check-single] Error 1
make[1]: Leaving directory `/home/pedro/gdb/keithcpp/build/gdb/testsuite'
make: *** [check] Error 2
I've no idea if this is compiler badness or not. I haven't investigated.
I also saw 1 FAIL->PASS in classes.exp, 2 new PASS->FAILs and 2 new FAIL->PASSes
in namespace.exp.
--
Pedro Alves
next prev parent reply other threads:[~2009-11-21 5:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 21:08 Keith Seitz
2009-11-21 5:21 ` Pedro Alves [this message]
2009-12-08 21:27 ` Keith Seitz
2009-11-21 17:12 ` Daniel Jacobowitz
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=200911210520.45772.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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