This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
Sunday Project gdb test results, 2001-06-23
- To: gdb-testers at sources dot redhat dot com
- Subject: Sunday Project gdb test results, 2001-06-23
- From: Michael Elizabeth Chastain <chastain at cygnus dot com>
- Date: Sun, 24 Jun 2001 23:06:49 -0700
Here are my Sunday Project results for 2001-06-23.
The merged results for all platforms contain 1 ERROR, 0 WARNINGs,
and 175 FAILs.
Native Red Hat Linux 6.0:
=== gdb Summary ===
# of ERRORs 0
# of WARNINGs 0
# of expected passes 7544
# of unexpected failures 132
# of unexpected successes 26
# of expected failures 195
# of untested testcases 1
# of unsupported tests 2
Native Red Hat Linux 6.1:
=== gdb Summary ===
# of ERRORs 0
# of WARNINGs 0
# of expected passes 7544
# of unexpected failures 132
# of unexpected successes 26
# of expected failures 195
# of untested testcases 1
# of unsupported tests 2
Native Red Hat Linux 6.2:
=== gdb Summary ===
# of ERRORs 0
# of WARNINGs 0
# of expected passes 7606
# of unexpected failures 143
# of unexpected successes 27
# of expected failures 194
# of untested testcases 1
Native Red Hat Linux 7:
=== gdb Summary ===
# of ERRORs 0
# of WARNINGs 0
# of expected passes 7614
# of unexpected failures 135
# of unexpected successes 26
# of expected failures 195
# of untested testcases 1
Native Solaris 2.5.1:
=== gdb Summary ===
# of ERRORs 1
# of WARNINGs 0
# of expected passes 7669
# of unexpected failures 112
# of unexpected successes 27
# of expected failures 194
# of unresolved testcases 33
# of untested testcases 1
Native Solaris 2.6:
=== gdb Summary ===
# of ERRORs 0
# of WARNINGs 0
# of expected passes 7669
# of unexpected failures 114
# of unexpected successes 27
# of expected failures 194
# of unresolved testcases 32
# of untested testcases 1
Native Solaris 2.7:
=== gdb Summary ===
# of ERRORs 1
# of WARNINGs 0
# of expected passes 7646
# of unexpected failures 135
# of unexpected successes 26
# of expected failures 195
# of unresolved testcases 33
# of untested testcases 1
Native Solaris 2.8:
=== gdb Summary ===
# of ERRORs 1
# of WARNINGs 0
# of expected passes 7641
# of unexpected failures 140
# of unexpected successes 26
# of expected failures 195
# of unresolved testcases 33
# of untested testcases 1
I ran the tests with FSF gcc cvs gcc-3_0-branch dated 2001-06-23 and FSF
gdb cvs dated 2001-06-23. gcc 3.0 has been released, but I am still using
the branch in anticipation that it will become gcc 3.0.1.
I revised my build process this week. Previously I built the current
sources with a Red Hat GnuPro toolchain. Now I have built stable Gnu
tools starting from the vendor's compiler and linker, and I use the
stable Gnu tools to build the current sources. My stable Gnu tools are:
make 3.79.1
binutils 2.11.2
gcc 3.0
flex 2.5.4a
bison 1.28
For testing, I still use a Red Hat GnuPro version of "expect".
I tried tcl8.3.3 and expect-5.32.1, but I ran into problems:
about 50 spurious ERRORs on native Solaris.
All hosts were available this week.
I counted the ERROR and WARNING lines by hand.
All results are in Terf, http://sources.redhat.com/cgi-bin/gdb.cgi .
Note that Terf does not report ERRORs or WARNINGs. Also, Terf has
problems with duplicate test names.
Here are the merged ERRORs categorized by test script:
1 TOTAL
= =====
1 gdb.base/shlib-call.exp
gdb.base/shlib-call.exp:
This script produces 1 ERROR on native Solaris 2.5.1, 2.7, and 2.8.
I have not analyzed this ERROR.
Here are the merged FAILs categorized by test script:
175 TOTAL
=== =====
2 gdb.base/annota1.exp
11 gdb.base/callfwmall.exp
4 gdb.base/completion.exp
1 gdb.base/corefile.exp
1 gdb.base/default.exp
2 gdb.base/ending-run.exp
2 gdb.base/page.exp
2 gdb.base/return2.exp
4 gdb.base/selftest.exp
8 gdb.base/shlib-call.exp
5 gdb.base/signals.exp
3 gdb.base/so-impl-ld.exp
6 gdb.base/step-line.exp
2 gdb.base/structs2.exp
2 gdb.c++/annota2.exp
18 gdb.c++/classes.exp
8 gdb.c++/cplusfuncs.exp
1 gdb.c++/demangle.exp
4 gdb.c++/derivation.exp
6 gdb.c++/inherit.exp
2 gdb.c++/local.exp
4 gdb.c++/method.exp
2 gdb.c++/namespace.exp
1 gdb.c++/overload.exp
6 gdb.c++/templates.exp
1 gdb.c++/userdef.exp
31 gdb.c++/virtfunc.exp
1 gdb.mi/mi-break.exp
1 gdb.mi/mi-console.exp
1 gdb.mi/mi-hack-cli.exp
2 gdb.mi/mi-regs.exp
1 gdb.mi/mi-simplerun.exp
6 gdb.mi/mi-stack.exp
1 gdb.mi/mi-var-cmd.exp
3 gdb.mi/mi-var-display.exp
1 gdb.mi/mi0-break.exp
1 gdb.mi/mi0-console.exp
1 gdb.mi/mi0-hack-cli.exp
2 gdb.mi/mi0-regs.exp
1 gdb.mi/mi0-simplerun.exp
6 gdb.mi/mi0-stack.exp
1 gdb.mi/mi0-var-cmd.exp
3 gdb.mi/mi0-var-display.exp
1 gdb.stabs/weird.exp
2 gdb.threads/pthreads.exp
1 gdb.trace/packetlen.exp
(Note that I now sort this list by script name rather than fail count).
The changes from 2001-06-16 are:
2001-06-16 total 142 FAILs
gdb.base/selftest.exp +1 FAILs gdb built with different compiler
gdb.mi/*.exp +32 FAILs new tests; gdb mi now enabled
2001-06-23 total 175 FAILs
gdb.base/selftest.exp:
selftest.exp invokes gdb on the gdb executable. Thus, this test is
sensitive to the compiler used to build gdb. This week I changed
from Red Hat Gnupro compilers to gcc 3.0 compilers. This is likely
to account for this change.
Note that the gdb test programs have always been built with the current
compiler from gcc-3_0-branch, and their results have not changed.
selftest.exp is unusual because it uses the gdb executable itself for
a test program.
gdb.mi/*.exp:
gdb has a new directory of MI tests, with about 1000 PASSing tests
and 32 FAILing tests. This is the first week for these tests.