This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
Sunday Project gdb test results, 2001-07-07
- To: gdb-testers at sources dot redhat dot com
- Subject: Sunday Project gdb test results, 2001-07-07
- From: Michael Elizabeth Chastain <chastain at cygnus dot com>
- Date: Sat, 7 Jul 2001 11:20:45 -0700
Here are my Sunday Project results for 2001-07-07.
The merged results for all platforms contain 2 build failures,
17 ERRORs, 0 WARNINGs and 174 FAILs.
Native hppa1.1-hp-hpux10.20:
Build failure, "make", gdb directory
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view&database=gdb&pr=63
Native hppa2.0w-hp-hpux11.00:
Build failure, "configure", opcodes directory
http://mail.gnu.org/pipermail/libtool-patches/2001-July/001309.html
http://mail.gnu.org/pipermail/libtool-patches/2001-July/001310.html
Workaround: setting CONFIG_SHELL=/bin/ksh probably works
Native i686-pc-linux-gnu (Red Hat Linux 6.0):
=== gdb Summary ===
# of ERRORs 16
# of WARNINGs 0
# of expected passes 7529
# of unexpected failures 132
# of unexpected successes 26
# of expected failures 195
# of unresolved testcases 15
# of untested testcases 1
# of unsupported tests 2
=== libiberty regress-demangle ===
All 645 tests passed
Native i686-pc-linux-gnu (Red Hat Linux 6.1):
=== gdb Summary ===
# of ERRORs 16
# of WARNINGs 0
# of expected passes 7531
# of unexpected failures 130
# of unexpected successes 26
# of expected failures 195
# of unresolved testcases 15
# of untested testcases 1
# of unsupported tests 2
=== libiberty regress-demangle ===
All 645 tests passed
Native i686-pc-linux-gnu (Red Hat Linux 6.2):
=== gdb Summary ===
# of ERRORs 16
# of WARNINGs 0
# of expected passes 7595
# of unexpected failures 139
# of unexpected successes 27
# of expected failures 194
# of unresolved testcases 15
# of untested testcases 1
=== libiberty regress-demangle ===
All 645 tests passed
Native i686-pc-linux-gnu (Red Hat Linux 7):
=== gdb Summary ===
# of ERRORs 16
# of WARNINGs 0
# of expected passes 7600
# of unexpected failures 134
# of unexpected successes 26
# of expected failures 195
# of unresolved testcases 15
# of untested testcases 1
=== libiberty regress-demangle ===
All 645 tests passed
Native sparc-sun-solaris2.5.1:
=== gdb Summary ===
# of ERRORs 1
# of WARNINGs 0
# of expected passes 7668
# of unexpected failures 113
# of unexpected successes 27
# of expected failures 194
# of unresolved testcases 33
# of untested testcases 1
=== libiberty regress-demangle ===
All 645 tests passed
Native sparc-sun-solaris2.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
=== libiberty regress-demangle ===
All 645 tests passed
Native sparc-sun-solaris2.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
=== libiberty regress-demangle ===
All 645 tests passed
Native sparc-sun-solaris2.8:
=== gdb Summary ===
# of ERRORs 1
# of WARNINGs 0
# of expected passes 7644
# of unexpected failures 137
# of unexpected successes 26
# of expected failures 195
# of unresolved testcases 33
# of untested testcases 1
=== libiberty regress-demangle ===
All 645 tests passed
I ran the tests with:
GNU Make version 3.79.1
GNU assembler version 2.11.2
GNU ld version 2.11.2
gcc version 3.0.1 20010628 (prerelease)
tcl 8.0.5
expect version 5.30.1
dejagnu (cvs 2001-07-07)
GNU gdb 2001-07-07-cvs (MI_OUT)
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:
17 TOTAL
== =====
1 gdb.base/shlib-call.exp
16 gdb.mi/mi-*.exp
There are no changes from 2001-06-29.
gdb.base/shlib-call.exp:
This script produces 1 ERROR on native sparc-sun-solaris-{2.5.1,2.7,2.8):
run
The program being debugged has been started already.
Start it from the beginning? (y or n) ERROR: Got interactive prompt.
UNRESOLVED: gdb.base/shlib-call.exp: re-run to bp in shared library (PR's 16495, 18213)
I have not analyzed this ERROR.
gdb.mi/mi-*.exp:
"ERROR: Breakpoints not deleted", gdb.mi/mi-*.exp, native linux
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view&database=gdb&pr=73
Here are the merged FAILs categorized by test script:
174 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
17 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-basics.exp
1 gdb.mi/mi-break.exp
1 gdb.mi/mi-console.exp
1 gdb.mi/mi-hack-cli.exp
3 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
1 gdb.trace/packetlen.exp
The changes from 2001-06-29 are:
2001-06-29 total 242 FAILs
gdb.base/annota1.exp -1 FAILs "warning: procfs: resume can't ..."
gdb.base/break.exp -1 FAILs "warning: procfs: resume can't ..."
gdb.base/call-rt-st.exp -1 FAILs "warning: procfs: resume can't ..."
gdb.base/ena-dis-br.exp -4 FAILs "warning: procfs: resume can't ..."
gdb.base/page.exp +1 FAILs dejagnu parser glitch
gdb.base/sigall.exp -1 FAILs "warning: procfs: resume can't ..."
gdb.base/signals.exp -2 FAILs "warning: procfs: resume can't ..."
gdb.base/watchpoint.exp -2 FAILs "warning: procfs: resume can't ..."
gdb.c++/annota2.exp -1 FAILs "warning: procfs: resume can't ..."
gdb.c++/classes.exp -1 FAILs test script fix
gdb.c++/method.exp -1 FAILs "warning: procfs: resume can't ..."
gdb.c++/ovldbreak.exp -12 FAILs "warning: procfs: resume can't ..."
gdb.mi/mi-hack-cli.exp -1 FAILs not analyzed
gdb.mi/mi-simplerun.exp -1 FAILs not analyzed
gdb.mi/mi-stack.exp -3 FAILs not analyzed
gdb.mi/mi-stepi.exp -1 FAILs not analyzed
gdb.mi/mi-var-block.exp -3 FAILs not analyzed
gdb.mi/mi-var-child.exp -3 FAILs not analyzed
gdb.mi/mi-var-cmd.exp -3 FAILs not analyzed
gdb.mi/mi-var-display.exp -5 FAILs not analyzed
gdb.mi/mi0-simplerun.exp -1 FAILs not analyzed
gdb.mi/mi0-stack.exp -3 FAILs not analyzed
gdb.mi/mi0-stepi.exp -1 FAILs not analyzed
gdb.mi/mi0-var-block.exp -3 FAILs not analyzed
gdb.mi/mi0-var-child.exp -4 FAILs not analyzed
gdb.mi/mi0-var-cmd.exp -3 FAILs not analyzed
gdb.mi/mi0-var-display.exp -5 FAILs not analyzed
gdb.threads/pthreads.exp -2 FAILs gdb fix
2001-07-07 total 174 FAILs
Most of the differences are due to PR gdb/74, which was fixed
this week:
"warning: procfs: resume can't find thread 1 -- resuming all."
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view&database=gdb&pr=74
http://sources.redhat.com/ml/gdb-cvs/2001-07/msg00038.html
FAIL: gdb.base/page.exp: info set
FAIL: gdb.base/page.exp: info set
The test script issues an "info set" command and looks at the result.
It actually does this twice, with identical test names.
This is a parsing or buffering issue in TCL/Expect/Dejagnu. The "info
set" command reports the current prompt, among many other things.
On sparc-sun-solaris2.8, Dejagnu takes that information in the middle
of the block and matches it against $gdb_prompt, casing two FAILs
(with the same name).
I changed my TCL/Expect/Dejagnu stack this week, which probably
explains the difference from last week.
FAIL: gdb.c++/classes.exp: ...
Pattern fix in the script.
FAIL: gdb.mi/*.exp: ...
Almost all of these were fallout from "resume can't find thread 1".
GDB MI is still new. I've never analyzed any of these FAILs.
FAIL: gdb.threads/pthreads.exp: some threads didn't run.
FAIL: gdb.threads/pthreads.exp: some threads didn't run.
Another pair of identical test names, gack.
Some thread changes were made in gdb this week, fixing the bug:
http://sources.redhat.com/ml/gdb-cvs/2001-07/msg00036.html
http://sources.redhat.com/ml/gdb-cvs/2001-07/msg00039.html