This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
gdb, native i686-pc-linux-gnu
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: gcc-testresults at gcc dot gnu dot org, gdb-testers at sources dot redhat dot com
- Date: Tue, 6 Apr 2004 23:47:05 -0400 (EDT)
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
I added gdb 6.0.91.
I added gdb 6.1, which came in a tarball named gdb-6.0.92.tar.bz2.
The contents of gdb 6.1 might change again.
My current tables are always at
http://www.shout.net/~mec/sunday/current/index.html
. Gdb Regression Summary
gdb drow_intercu-20040221-branch versus gdb HEAD
gdb drow-cplus-branch versus gdb HEAD
Not analyzed.
gdb HEAD versus gdb 6.0
gdb/931 gdb/1505 gdb/1512 gdb/1516 gdb/1588
gdb 6.1 versus gdb 6.0
gdb/931 gdb/1505 gdb/1512 gdb/1516 gdb/1588
gdb 6.0.91 versus gdb 6.0
gdb/931 gdb/1505 gdb/1512 gdb/1516 gdb/1588
gdb gdb_6_1-branch versus gdb 6.0
gdb/931 gdb/1505 gdb/1512 gdb/1516 gdb/1588
. Gcc Regression Summary
gcc tree-ssa-20020619-branch versus gcc 3.3.3
gcc/14048 gcc/14049
gcc HEAD versus gcc 3.3.3
gcc/12267 gcc/13708 gcc/13956 gcc/13974 gcc/14860
gdb/1537 gdb/1540
gcc gcc-3_4-branch versus gcc 3.3.3
gcc/12267 gcc/13708 gcc/13956
gdb/1537 gdb/1540
gcc gcc-3_3-branch versus gcc 3.3.3
no improvements and no regressions
. Binutils Regression Summary
binutils HEAD versus binutils 2.14
binutils binutils-2_15-branch versus binutils 2.14
gdb.base/shlib-call.exp unanalyzed regressions
. Old Bugs Fixed Since Last Spin
. gcc gcc-3_4-branch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13974
[3.5 regression] bad line marker in debug info
Jan H fixed this bug on the branch, although this bug still
happened with gcc HEAD and gcc tree-ssa-20020619-branch.
. New Bugs Detected Since Last Spin
. gcc HEAD
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14860
[regression] gcc -gstabs+ fails to emit stabs for fundamental types
. gcc tree-ssa-20020619-branch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14860
[regression] gcc -gstabs+ fails to emit stabs for fundamental types
. PR Count
Query executed 2004-04-04 18:23:29 UTC
1604 matches found
22 analyzed
746 closed
24 feedback
793 open
3 paperwork
16 suspended
1604 TOTAL
. Libiberty Testing
. target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
binutils binutils-2_15-branch 742 tests, 0 failures
binutils HEAD 745 tests, 0 failures
gcc gcc-3_3-branch 649 tests, 0 failures
gcc gcc-3_4-branch 745 tests, 0 failures
gcc HEAD 745 tests, 0 failures
gcc tree-ssa-20020619-branch 745 tests, 0 failures
gdb HEAD 745 tests, 0 failures
gdb drow-cplus-branch 742 tests, 0 failures
gdb drow_intercu-20040221-branch 745 tests, 0 failures
gdb gdb_6_1-branch 745 tests, 0 failures
For gcc tests, the test results are with binutils 2.14.
The binutils version should not make a difference.
. Gdb Testing
My tables are at
http://www.shout.net/~mec/sunday/2004-04-01/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-03-20/index.html
. Non-Pass Results
gdb 6.0
suite 6.0 1114 non-PASS results
suite HEAD 1213 non-PASS results
gdb 6.0.91
suite 6.0.91 1030 non-PASS results
suite HEAD 1033 non-PASS results
gdb 6.1
suite 6.1 1031 non-PASS results
suite HEAD 1033 non-PASS results
gdb gdb_6_1-banch
suite gdb_6_1-branch 1031 non-PASS results
suite HEAD 1032 non-PASS results
gdb HEAD
suite HEAD 1041 non-PASS results
gdb drow-cplus-branch
suite drow-cplus-branch 1273 non-PASS results
suite HEAD 1215 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 1035 non-PASS results
suite HEAD 1033 non-PASS results
I run each version of gdb with two test suites: the test suite that
comes with that version of gdb and the test suite that comes with
gdb HEAD.
. gdb 6.0
. suite 6.0
. gdb.base/break.exp: run until function breakpoint, optimized file
FAIL -> PASS
gcc HEAD -gstabs+ improved.
gdb now shows the arguments to main.
. gdb.base/call-strs.exp: *
gdb.base/callfuncs.exp: *
gdb.base/completion.exp: *
gdb.base/constvars.exp: *
gdb.base/dbx.exp: *
gdb.base/maint.exp: *
gdb.base/miscexprs.exp: *
gdb.base/opaque.exp: *
gdb.base/pointers.exp: *
gdb.base/printcmds.exp: *
gdb.base/ptype.exp: *
gdb.base/volatile.exp: *
gdb.base/whatis-exp.exp: *
gdb.base/whatis.exp: *
gdb.mi/mi-stack.exp: *
gdb.mi/mi-var-block.exp: *
gdb.mi/mi-var-child.exp: *
gdb.mi/mi-var-cmd.exp: *
gdb.mi/mi-var-display.exp: *
gdb.mi/mi1-stack.exp: *
gdb.mi/mi1-var-block.exp: *
gdb.mi/mi1-var-child.exp: *
gdb.mi/mi1-var-cmd.exp: *
gdb.mi/mi1-var-display.exp: *
gdb.mi/mi2-stack.exp: *
gdb.mi/mi2-var-block.exp: *
gdb.mi/mi2-var-child.exp: *
gdb.mi/mi2-var-cmd.exp: *
gdb.mi/mi2-var-display.exp: *
PASS -> FAIL
XPASS -> XFAIL
XFAIL -> FAIL
gcc HEAD -gstabs+ and gcc tree-ssa-20020619-branch -gstabs+
regressed.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14860
[regression] gcc -gstabs+ fails to emit stabs for fundamental types
The symptom is:
(gdb) print s
$2 = (<invalid type code 7> *) "test string"
. gdb.mi/mi*-pthreads.exp: check mi_thread_command_set: -thread-select [3456]
blank -> PASS
PASS -> blank
When gdb operates on an inferior program with threads, gdb uses
hidden breakpoints in the thread library to track events such as
thread creation and thread destruction.
This causes some programs to behave differently because they
aren't prepared to handle the additional signals caused by the
hidden breakpoints. The test program for mi*-pthreads.exp is
such a program.
http://sources.redhat.com/ml/gdb/2003-09/msg00279.html
http://sources.redhat.com/gdb/bugs/259
. gdb.mi/mi-until.exp: until after current function
gdb.mi/mi1-until.exp: until after current function
gdb.mi/mi2-until.exp: until after current function
FAIL -> PASS
Jan H fixed a bug in gcc gcc-3_4-branch.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13974
[3.5 regression] bad line marker in debug info
This bug still happens with gcc HEAD and gcc
tree-ssa-20020619-branch.
. gdb.threads/schedlock.exp: *
PASS
gdb.threads/schedlock.exp: thread 0 ran (didn't run)
gdb.threads/schedlock.exp: thread 1 ran (didn't run)
gdb.threads/schedlock.exp: thread 2 ran (didn't run)
gdb.threads/schedlock.exp: thread 3 ran (didn't run)
gdb.threads/schedlock.exp: thread 4 ran (didn't run)
gdb.threads/schedlock.exp: thread 5 ran (didn't run)
PASS
FAIL
All tests PASSed in all configurations except for the
"thread N ran" tests. Here are the counts per thread.
PASS FAIL
thread 0 5 33
thread 1 37 1
thread 2 38 0
thread 3 38 0
thread 4 38 0
thread 5 38 0
. gdb 6.0
. suite HEAD
. gdb.base/auxv.exp: *
blank -> WARNING
WARNING -> blank
PASS -> blank
PASS -> FAIL
PASS -> UNSUPPORTED
FAIL -> UNSUPPORTED
Not analyzed. The behavior of this test script with gdb 6.0
is not interesting.
. gdb.base/bigcore.exp: extract next heap
blank -> PASS
gdb.base/bigcore.exp: extract next heap (stop at 50)
PASS -> blank
gdb.base/bigcore.exp: extract prev heap
blank -> PASS
gdb.base/bigcore.exp: extract prev heap (stop at 50)
PASS -> blank
Not analyzed. Probably harmless. I might have changed
the size of the swap space on my test bed.
. gdb.base/break.exp: run until function breakpoint, optimized file
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/call-strs.exp: *
gdb.base/callfuncs.exp: *
gdb.base/completion.exp: *
gdb.base/constvars.exp: *
gdb.base/dbx.exp: *
gdb.base/maint.exp: *
gdb.base/miscexprs.exp: *
gdb.base/opaque.exp: *
gdb.base/pointers.exp: *
gdb.base/printcmds.exp: *
gdb.base/ptype.exp: *
gdb.base/volatile.exp: *
gdb.base/whatis-exp.exp: *
gdb.base/whatis.exp: *
gdb.mi/mi-stack.exp: *
gdb.mi/mi-var-block.exp: *
gdb.mi/mi-var-child.exp: *
gdb.mi/mi-var-cmd.exp: *
gdb.mi/mi-var-display.exp: *
gdb.mi/mi2-stack.exp: *
gdb.mi/mi2-var-block.exp: *
gdb.mi/mi2-var-child.exp: *
gdb.mi/mi2-var-cmd.exp: *
gdb.mi/mi2-var-display.exp: *
PASS -> FAIL
XFAIL -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/freebpcmd.exp: run program with breakpoint commands
KFAIL -> KFAIL
This is a non-deterministic memory corruption bug in gdb 6.0.
It has been fixed in gdb HEAD.
http://sources.redhat.com/gdb/bugs/1489
GDB crashes executing breakpoint commands that continue the inferior
. gdb.mi/mi-until.exp: until after current function
gdb.mi/mi2-until.exp: until after current function
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.threads/schedlock.exp: *
PASS
gdb.threads/schedlock.exp: thread 0 ran (didn't run)
gdb.threads/schedlock.exp: thread 1 ran (didn't run)
gdb.threads/schedlock.exp: thread 2 ran (didn't run)
gdb.threads/schedlock.exp: thread 3 ran (didn't run)
gdb.threads/schedlock.exp: thread 4 ran (didn't run)
gdb.threads/schedlock.exp: thread 5 ran (didn't run)
PASS
FAIL
All tests PASSed in all configurations except for the
"thread N ran" tests. Here are the counts per thread.
PASS FAIL
thread 0 2 10
thread 1 11 1
thread 2 11 1
thread 3 11 1
thread 4 11 1
thread 5 12 0
. gdb 6.0.91
. suite 6.0.91
This is the first spin for gdb 6.0.91.
I did not analyze these results.
. suite HEAD
This is the first spin for gdb 6.0.91.
I compared gdb 6.0.91 suite HEAD, gdb 6.1 suite HEAD, and gdb
gdb-6_1-branch suite HEAD. There were no significant differences.
. gdb 6.1
. suite 6.1
This is actually gdb 6.0.92, a prerelease version of gdb 6.1.
This is the first spin for gdb 6.1.
I did not analyze these results.
. suite HEAD
This is actually gdb 6.0.92, a prerelease version of gdb 6.1.
This is the first spin for gdb 6.1.
I compared gdb 6.0.91 suite HEAD, gdb 6.1 suite HEAD, and gdb
gdb-6_1-branch suite HEAD. There were no significant differences.
. gdb gdb_6_1-branch
. suite gdb_6_1-branch
. gdb.base/bigcore.exp: extract next heap
blank -> PASS
gdb.base/bigcore.exp: extract next heap (stop at 50)
PASS -> blank
gdb.base/bigcore.exp: extract prev heap
blank -> PASS
gdb.base/bigcore.exp: extract prev heap (stop at 50)
PASS -> blank
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/break.exp: run until function breakpoint, optimized file
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/call-strs.exp: *
gdb.base/callfuncs.exp: *
gdb.base/completion.exp: *
gdb.base/constvars.exp: *
gdb.base/dbx.exp: *
gdb.base/maint.exp: *
gdb.base/miscexprs.exp: *
gdb.base/opaque.exp: *
gdb.base/pointers.exp: *
gdb.base/printcmds.exp: *
gdb.base/ptype.exp: *
gdb.base/volatile.exp: *
gdb.base/whatis-exp.exp: *
gdb.base/whatis.exp: *
gdb.mi/mi-stack.exp: *
gdb.mi/mi-var-block.exp: *
gdb.mi/mi-var-child.exp: *
gdb.mi/mi-var-cmd.exp: *
gdb.mi/mi-var-display.exp: *
gdb.mi/mi2-stack.exp: *
gdb.mi/mi2-var-block.exp: *
gdb.mi/mi2-var-child.exp: *
gdb.mi/mi2-var-cmd.exp: *
gdb.mi/mi2-var-display.exp: *
PASS -> FAIL
XFAIL -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/gdb1250.exp: setting breakpoint at abort
FAIL -> blank
gdb.base/gdb1250.exp: couldn't run to breakpoint
ERROR -> blank
gdb.base/gdb1250.exp: backtrace from abort
blank -> PASS
gdb.base/gdb1476.exp: continue to null pointer call
UNRESOLVED -> PASS
Daniel J fixed a bug in lib/gdb.exp.
This happened with binutils binutils-2_15-branch
and binutils HEAD.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Fluctuation in test result probably due to a signal handling
race in the command loop.
http://sources.redhat.com/gdb/bugs/544
gdb.c++/annota2.exp: annotate-quit test sometimes fails
. gdb.mi/mi-until.exp: until after current function
gdb.mi/mi2-until.exp: until after current function
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
PASS -> blank
Fluctuation with unknown cause. Probably harmless.
. gdb.threads/schedlock.exp: *
PASS
gdb.threads/schedlock.exp: thread 0 ran (didn't run)
gdb.threads/schedlock.exp: thread 1 ran (didn't run)
gdb.threads/schedlock.exp: thread 2 ran (didn't run)
gdb.threads/schedlock.exp: thread 3 ran (didn't run)
gdb.threads/schedlock.exp: thread 4 ran (didn't run)
gdb.threads/schedlock.exp: thread 5 ran (didn't run)
PASS
FAIL
All tests PASSed in all configurations except for the
"thread N ran" tests. Here are the counts per thread.
PASS FAIL
thread 0 4 34
thread 1 32 6
thread 2 38 0
thread 3 36 2
thread 4 37 1
thread 5 38 0
. gdb gdb_6_1-branch
. suite HEAD
. gdb.base/bigcore.exp: extract next heap
blank -> PASS
gdb.base/bigcore.exp: extract next heap (stop at 50)
PASS -> blank
gdb.base/bigcore.exp: extract prev heap
blank -> PASS
gdb.base/bigcore.exp: extract prev heap (stop at 50)
PASS -> blank
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/break.exp: run until function breakpoint, optimized file
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/call-strs.exp: *
gdb.base/callfuncs.exp: *
gdb.base/completion.exp: *
gdb.base/constvars.exp: *
gdb.base/dbx.exp: *
gdb.base/maint.exp: *
gdb.base/miscexprs.exp: *
gdb.base/opaque.exp: *
gdb.base/pointers.exp: *
gdb.base/printcmds.exp: *
gdb.base/ptype.exp: *
gdb.base/volatile.exp: *
gdb.base/whatis-exp.exp: *
gdb.base/whatis.exp: *
gdb.mi/mi-stack.exp: *
gdb.mi/mi-var-block.exp: *
gdb.mi/mi-var-child.exp: *
gdb.mi/mi-var-cmd.exp: *
gdb.mi/mi-var-display.exp: *
gdb.mi/mi2-stack.exp: *
gdb.mi/mi2-var-block.exp: *
gdb.mi/mi2-var-child.exp: *
gdb.mi/mi2-var-cmd.exp: *
gdb.mi/mi2-var-display.exp: *
PASS -> FAIL
XFAIL -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
Same analysis as gdb gdb_6_1-branch suite gdb_6_1-branch.
. gdb.mi/mi-until.exp: until after current function
gdb.mi/mi2-until.exp: until after current function
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.threads/schedlock.exp: *
PASS
gdb.threads/schedlock.exp: thread 0 ran (didn't run)
gdb.threads/schedlock.exp: thread 1 ran (didn't run)
gdb.threads/schedlock.exp: thread 2 ran (didn't run)
gdb.threads/schedlock.exp: thread 3 ran (didn't run)
gdb.threads/schedlock.exp: thread 4 ran (didn't run)
gdb.threads/schedlock.exp: thread 5 ran (didn't run)
PASS
FAIL
All tests PASSed in all configurations except for the
"thread N ran" tests. Here are the counts per thread.
PASS FAIL
thread 0 0 12
thread 1 12 0
thread 2 12 0
thread 3 12 0
thread 4 12 0
thread 5 12 0
. gdb HEAD
. suite HEAD
. gdb.base/bigcore.exp: extract next heap
blank -> PASS
gdb.base/bigcore.exp: extract next heap (stop at 50)
PASS -> blank
gdb.base/bigcore.exp: extract prev heap
blank -> PASS
gdb.base/bigcore.exp: extract prev heap (stop at 50)
PASS -> blank
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/break.exp: run until function breakpoint, optimized file
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/call-strs.exp: *
gdb.base/callfuncs.exp: *
gdb.base/completion.exp: *
gdb.base/constvars.exp: *
gdb.base/dbx.exp: *
gdb.base/maint.exp: *
gdb.base/miscexprs.exp: *
gdb.base/opaque.exp: *
gdb.base/pointers.exp: *
gdb.base/printcmds.exp: *
gdb.base/ptype.exp: *
gdb.base/volatile.exp: *
gdb.base/whatis-exp.exp: *
gdb.base/whatis.exp: *
gdb.mi/mi-stack.exp: *
gdb.mi/mi-var-block.exp: *
gdb.mi/mi-var-child.exp: *
gdb.mi/mi-var-cmd.exp: *
gdb.mi/mi-var-display.exp: *
gdb.mi/mi2-stack.exp: *
gdb.mi/mi2-var-block.exp: *
gdb.mi/mi2-var-child.exp: *
gdb.mi/mi2-var-cmd.exp: *
gdb.mi/mi2-var-display.exp: *
PASS -> FAIL
XFAIL -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/gdb1250.exp: setting breakpoint at abort
FAIL -> blank
gdb.base/gdb1250.exp: couldn't run to breakpoint
ERROR -> blank
gdb.base/gdb1250.exp: backtrace from abort
blank -> PASS
gdb.base/gdb1476.exp: continue to null pointer call
UNRESOLVED -> PASS
Same analysis as gdb gdb_6_1-branch suite gdb_6_1-branch.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb gdb_6_1-branch suite gdb_6_1-branch.
. gdb.mi/mi-until.exp: until after current function
gdb.mi/mi2-until.exp: until after current function
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.threads/schedlock.exp: *
PASS
gdb.threads/schedlock.exp: thread 0 ran (didn't run)
gdb.threads/schedlock.exp: thread 1 ran (didn't run)
gdb.threads/schedlock.exp: thread 2 ran (didn't run)
gdb.threads/schedlock.exp: thread 3 ran (didn't run)
gdb.threads/schedlock.exp: thread 4 ran (didn't run)
gdb.threads/schedlock.exp: thread 5 ran (didn't run)
PASS
FAIL
All tests PASSed in all configurations except for the
"thread N ran" tests. Here are the counts per thread.
PASS FAIL
thread 0 3 35
thread 1 35 3
thread 2 37 1
thread 3 38 0
thread 4 37 1
thread 5 38 0
. gdb drow-cplus-branch
. suite drow-cplus-branch
. gdb.base/break.exp: run until function breakpoint, optimized file
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/call-strs.exp: *
gdb.base/callfuncs.exp: *
gdb.base/completion.exp: *
gdb.base/constvars.exp: *
gdb.base/dbx.exp: *
gdb.base/maint.exp: *
gdb.base/miscexprs.exp: *
gdb.base/opaque.exp: *
gdb.base/pointers.exp: *
gdb.base/printcmds.exp: *
gdb.base/ptype.exp: *
gdb.base/volatile.exp: *
gdb.base/whatis-exp.exp: *
gdb.base/whatis.exp: *
gdb.mi/mi-stack.exp: *
gdb.mi/mi-var-block.exp: *
gdb.mi/mi-var-child.exp: *
gdb.mi/mi-var-cmd.exp: *
gdb.mi/mi-var-display.exp: *
gdb.mi/mi1-stack.exp: *
gdb.mi/mi1-var-block.exp: *
gdb.mi/mi1-var-child.exp: *
gdb.mi/mi1-var-cmd.exp: *
gdb.mi/mi1-var-display.exp: *
gdb.mi/mi2-stack.exp: *
gdb.mi/mi2-var-block.exp: *
gdb.mi/mi2-var-child.exp: *
gdb.mi/mi2-var-cmd.exp: *
gdb.mi/mi2-var-display.exp: *
PASS -> FAIL
XFAIL -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.mi/mi-until.exp: until after current function
gdb.mi/mi1-until.exp: until after current function
gdb.mi/mi2-until.exp: until after current function
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.threads/schedlock.exp: *
PASS
gdb.threads/schedlock.exp: thread 0 ran (didn't run)
gdb.threads/schedlock.exp: thread 1 ran (didn't run)
gdb.threads/schedlock.exp: thread 2 ran (didn't run)
gdb.threads/schedlock.exp: thread 3 ran (didn't run)
gdb.threads/schedlock.exp: thread 4 ran (didn't run)
gdb.threads/schedlock.exp: thread 5 ran (didn't run)
PASS
FAIL
All tests PASSed in all configurations except for the
"thread N ran" tests. Here are the counts per thread.
PASS FAIL
thread 0 3 9
thread 1 9 3
thread 2 11 1
thread 3 11 1
thread 4 11 1
thread 5 12 0
. gdb drow-cplus-branch
. suite HEAD
. gdb.base/bigcore.exp: extract next heap
blank -> PASS
gdb.base/bigcore.exp: extract next heap (stop at 50)
PASS -> blank
gdb.base/bigcore.exp: extract prev heap
blank -> PASS
gdb.base/bigcore.exp: extract prev heap (stop at 50)
PASS -> blank
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/break.exp: run until function breakpoint, optimized file
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/call-strs.exp: *
gdb.base/callfuncs.exp: *
gdb.base/completion.exp: *
gdb.base/constvars.exp: *
gdb.base/dbx.exp: *
gdb.base/maint.exp: *
gdb.base/miscexprs.exp: *
gdb.base/opaque.exp: *
gdb.base/pointers.exp: *
gdb.base/printcmds.exp: *
gdb.base/ptype.exp: *
gdb.base/volatile.exp: *
gdb.base/whatis-exp.exp: *
gdb.base/whatis.exp: *
gdb.mi/mi-stack.exp: *
gdb.mi/mi-var-block.exp: *
gdb.mi/mi-var-child.exp: *
gdb.mi/mi-var-cmd.exp: *
gdb.mi/mi-var-display.exp: *
gdb.mi/mi2-stack.exp: *
gdb.mi/mi2-var-block.exp: *
gdb.mi/mi2-var-child.exp: *
gdb.mi/mi2-var-cmd.exp: *
gdb.mi/mi2-var-display.exp: *
PASS -> FAIL
XFAIL -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/langs.exp: *
blank -> PASS
blank -> UNRESOLVED
ERROR -> blank
UNRESOLVED -> blank
Not analyzed.
. gdb.base/pending.exp: *
blank -> ERROR
blank -> FAIL
ERROR -> blank
PASS -> FAIL
PASS -> UNRESOLVED
FAIL -> blank
FAIL -> PASS
FAIL -> UNRESOLVED
UNRESOLVED -> PASS
UNRESOLVED -> FAIL
Not analyzed.
. gdb.cp/rtti.exp: Process no longer exists
ERROR -> blank
gdb.cp/rtti.exp: print *obj3
UNRESOLVED -> FAIL
Not analyzed.
. gdb.mi/mi-until.exp: until after current function
gdb.mi/mi2-until.exp: until after current function
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.threads/schedlock.exp: *
PASS
gdb.threads/schedlock.exp: thread 0 ran (didn't run)
gdb.threads/schedlock.exp: thread 1 ran (didn't run)
gdb.threads/schedlock.exp: thread 2 ran (didn't run)
gdb.threads/schedlock.exp: thread 3 ran (didn't run)
gdb.threads/schedlock.exp: thread 4 ran (didn't run)
gdb.threads/schedlock.exp: thread 5 ran (didn't run)
PASS
FAIL
All tests PASSed in all configurations except for the
"thread N ran" tests. Here are the counts per thread.
PASS FAIL
thread 0 0 12
thread 1 10 2
thread 2 12 0
thread 3 12 0
thread 4 12 0
thread 5 12 0
. gdb drow_intercu-20040221-branch
. suite drow_intercu-20040221-branch
. gdb.base/auxv.exp: *
blank -> WARNING
blank -> PASS
blank -> FAIL
blank -> UNSUPPORTED
gdb.base/charset.exp: check value of "\e" in *
gdb.base/charset.exp: check value of '\e' in *
gdb.base/charset.exp: try printing '\e' in *
PASS -> blank
gdb.base/setvar.exp: *
blank -> PASS
PASS -> blank
gdb.cp/class2.exp: print object with no data fields
blank -> PASS
gdb.cp/classes.exp: *
FAIL -> PASS
FAIL -> KFAIL
KFAIL -> KFAIL
gdb.cp/local.exp: ptype NestedInnerLocal
FAIL -> PASS
gdb.cp/namespace.exp: ptype CClass::NEstedClass
FAIL -> PASS
gdb.cp/pr-1553.exp: ptype E::F
gdb.cp/pr-1553.exp: ptype c_var
blank -> PASS
blank -> FAIL
gdb.cp/rtti.exp: continue to breakpoint: end of constructors in func3
blank -> PASS
gdb.cp/rtti.exp: print *obj3
blank -> PASS
blank -> FAIL
gdb.cp/templates.exp: ptype Baz
KFAIL -> FAIL
gdb.cp/templates.exp: ptype quxint
FAIL -> PASS
gdb.java/jmisc.exp: *
blank -> FAIL
FAIL -> blank
FAIL -> PASS
gdb.stabs/weird.exp: print very big integer
FAIL -> PASS
Daniel J merged from gdb HEAD and suite HEAD.
. gdb.base/bigcore.exp: extract next heap
blank -> PASS
gdb.base/bigcore.exp: extract next heap (stop at 50)
PASS -> blank
gdb.base/bigcore.exp: extract prev heap
blank -> PASS
gdb.base/bigcore.exp: extract prev heap (stop at 50)
PASS -> blank
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/break.exp: run until function breakpoint, optimized file
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/call-strs.exp: *
gdb.base/callfuncs.exp: *
gdb.base/completion.exp: *
gdb.base/constvars.exp: *
gdb.base/dbx.exp: *
gdb.base/maint.exp: *
gdb.base/miscexprs.exp: *
gdb.base/opaque.exp: *
gdb.base/pointers.exp: *
gdb.base/printcmds.exp: *
gdb.base/ptype.exp: *
gdb.base/volatile.exp: *
gdb.base/whatis-exp.exp: *
gdb.base/whatis.exp: *
gdb.mi/mi-stack.exp: *
gdb.mi/mi-var-block.exp: *
gdb.mi/mi-var-child.exp: *
gdb.mi/mi-var-cmd.exp: *
gdb.mi/mi-var-display.exp: *
gdb.mi/mi2-stack.exp: *
gdb.mi/mi2-var-block.exp: *
gdb.mi/mi2-var-child.exp: *
gdb.mi/mi2-var-cmd.exp: *
gdb.mi/mi2-var-display.exp: *
PASS -> FAIL
XFAIL -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb gdb_6_1-branch suite gdb_6_1-branch.
. gdb.mi/mi-until.exp: until after current function
gdb.mi/mi2-until.exp: until after current function
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
blank -> PASS
Same analysis as gdb gdb_6-1branch suite gdb_6-1-branch.
. gdb.threads/schedlock.exp: *
PASS
gdb.threads/schedlock.exp: thread 0 ran (didn't run)
gdb.threads/schedlock.exp: thread 1 ran (didn't run)
gdb.threads/schedlock.exp: thread 2 ran (didn't run)
gdb.threads/schedlock.exp: thread 3 ran (didn't run)
gdb.threads/schedlock.exp: thread 4 ran (didn't run)
gdb.threads/schedlock.exp: thread 5 ran (didn't run)
PASS
FAIL
All tests PASSed in all configurations except for the
"thread N ran" tests. Here are the counts per thread.
PASS FAIL
thread 0 2 10
thread 1 10 2
thread 2 11 1
thread 3 12 0
thread 4 11 1
thread 5 12 0
. gdb drow_intercu-20040221-branch
. suite HEAD
. gdb.base/auxv.exp: Unrecognized output: No auxilary vector found, or failed reading it.
WARNING -> blank
Not analyzed.
. gdb.base/bigcore.exp: extract next heap
blank -> PASS
gdb.base/bigcore.exp: extract next heap (stop at 50)
PASS -> blank
gdb.base/bigcore.exp: extract prev heap
blank -> PASS
gdb.base/bigcore.exp: extract prev heap (stop at 50)
PASS -> blank
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/break.exp: run until function breakpoint, optimized file
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/call-strs.exp: *
gdb.base/callfuncs.exp: *
gdb.base/completion.exp: *
gdb.base/constvars.exp: *
gdb.base/dbx.exp: *
gdb.base/maint.exp: *
gdb.base/miscexprs.exp: *
gdb.base/opaque.exp: *
gdb.base/pointers.exp: *
gdb.base/printcmds.exp: *
gdb.base/ptype.exp: *
gdb.base/volatile.exp: *
gdb.base/whatis-exp.exp: *
gdb.base/whatis.exp: *
gdb.mi/mi-stack.exp: *
gdb.mi/mi-var-block.exp: *
gdb.mi/mi-var-child.exp: *
gdb.mi/mi-var-cmd.exp: *
gdb.mi/mi-var-display.exp: *
gdb.mi/mi2-stack.exp: *
gdb.mi/mi2-var-block.exp: *
gdb.mi/mi2-var-child.exp: *
gdb.mi/mi2-var-cmd.exp: *
gdb.mi/mi2-var-display.exp: *
PASS -> FAIL
XFAIL -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/langs.exp: *
blank -> PASS
ERROR -> blank
UNRESOLVED -> blank
UNRESOLVED -> PASS
Not analyzed.
. gdb.base/pending.exp: *
ERROR -> blank
FAIL -> blank
FAIL -> PASS
UNRESOLVED -> PASS
Not analyzed.
. gdb.base/printcmds.exp: p &ctable1[3*8]
gdb.base/printcmds.exp: p ctable1[27]
FAIL -> PASS
Daniel J merged from gdb HEAD. These tests are sensitive to
the representation of the escape character as '\e' or '\033'.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb gdb_6_1-branch suite gdb_6_1-branch.
. gdb.cp/namespace.exp: ptype CClass::NEstedClass
FAIL -> PASS
Not analyzed.
. gdb.cp/pr-1553.exp: ptype E::F
gdb.cp/pr-1553.exp: ptype c_var
FAIL -> PASS
Not analyzed.
. gdb.cp/rtti.exp: Process no longer exists
ERROR -> blank
gdb.cp/rtti.exp: print *obj3
UNRESOLVED -> PASS
Not analyzed.
. gdb.cp/templates.exp: ptype Baz
KFAIL -> FAIL
Not analyzed.
. gdb.mi/mi-until.exp: until after current function
gdb.mi/mi2-until.exp: until after current function
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.stabs/weird.exp: print very big integer
FAIL -> PASS
Same analysis as gdb drow_intercu-20040221-branch suite drow_intercu-20040221-branch.
. gdb.threads/schedlock.exp: *
PASS
gdb.threads/schedlock.exp: thread 0 ran (didn't run)
gdb.threads/schedlock.exp: thread 1 ran (didn't run)
gdb.threads/schedlock.exp: thread 2 ran (didn't run)
gdb.threads/schedlock.exp: thread 3 ran (didn't run)
gdb.threads/schedlock.exp: thread 4 ran (didn't run)
gdb.threads/schedlock.exp: thread 5 ran (didn't run)
PASS
FAIL
All tests PASSed in all configurations except for the
"thread N ran" tests. Here are the counts per thread.
PASS FAIL
thread 0 2 10
thread 1 11 1
thread 2 12 0
thread 3 12 0
thread 4 12 0
thread 5 12 0
. Package Versions
. This Spin
binutils HEAD 2004-03-30 21:04:08 UTC
binutils binutils-2_15-branch 2004-03-30 21:06:52 UTC
gcc tree-ssa-20020619-branch 2004-03-30 21:09:29 UTC
gcc HEAD 2004-03-30 21:16:48 UTC
gcc gcc-3_4-branch 2004-03-30 21:26:44 UTC
gcc gcc-3_3-branch 2004-03-30 21:33:00 UTC
gdb HEAD 2004-04-01 07:44:52 UTC
gdb drow-cplus-branch 2004-04-01 07:47:13 UTC
gdb drow_intercu-20040221-branch 2004-04-01 07:49:48 UTC
gdb gdb_6_1-branch 2004-04-01 07:52:21 UTC
. Last Spin
binutils HEAD 2004-03-19 17:26:47 UTC
binutils binutils-2_15-branch 2004-03-19 17:29:10 UTC
gcc tree-ssa-20020619-branch 2004-03-19 17:58:10 UTC
gcc HEAD 2004-03-19 18:06:06 UTC
gcc gcc-3_4-branch 2004-03-19 18:11:56 UTC
gcc gcc-3_3-branch 2004-03-19 18:18:14 UTC
gdb HEAD 2004-03-21 00:58:16 UTC
gdb drow-cplus-branch 2004-03-21 01:00:35 UTC
gdb drow_intercu-20040221-branch 2004-03-21 01:02:37 UTC
gdb gdb_6_1-branch 2004-03-21 01:04:44 UTC
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
dejagnu => dejagnu 1.4.4
expect => expect 5.39
tcl => tcl 8.4.5
gdb => 6.0, 6.0.91, 6.1, gdb_6_1-branch, HEAD, drow-cplus-branch, drow_intercu-20040221-branch
suite => 6.0, 6.0.91, 6.1, gdb_6_1-branch, HEAD, drow-cplus-branch, drow_intercu-20040221-branch
cc => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.3, gcc gcc-3_3-branch, gcc gcc-3_4-branch, gcc HEAD, gcc tree-ssa-20020619-branch
as => binutils 2.13.90.0.2-rh, binutils 2.14, binutils binutils-2_15-branch, binutils HEAD
ld => binutils 2.13.90.0.2-rh, binutils 2.14, binutils binutils-2_15-branch, binutils HEAD
libc => glibc 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count => 286
'target' and 'host' are gnu configuration triples.
'osversion' is the host operating system name, which is additional
information beyond 'host'.
'tcl', 'expect', and 'dejagnu' are host packages to run tests.
'suite' is the version name of the gdb test suite.
'gdb' is a version name.
'cc', 'as', 'ld', and 'libc' are package names.
versions starting with a digit are official releases or snapshots.
versions starting with a digit and ending with '-rh' are
vendor-supplied official releases on my red hat linux host.
versions named 'HEAD' are the cvs HEAD, also known as 'mainline' or 'trunk'.
versions with any other name are cvs branches.
'gformat' is the debugging information format.
'glevel' is the debugging level.
'count' is the total number of configurations tested.
as/ld are always matched.
The vendor gcc is available only with vendor as/ld.
The vendor as/ld are tested only with vendor gcc.
I test most configurations only with as binutils 2.14 and ld binutils
2.14. I test gdb 6.0 suite 6.0, gdb 6.0.91 suite 6.0.91, gdb 6.1
suite 6.1, gdb gdb_6_1-branch suite gdb_6-1-branch, and gdb HEAD suite
HEAD with the full spectrum of as and ld.
. Host Software
. host=i686-pc-linux-gnu, osversion=red-hat-8.0
make 3.79.1
binutils 2.14
gcc 3.3.2
flex 2.5.4
bison 1.875
tcl 8.4.5
expect 5.39
dejagnu 1.4.4
The sources.redhat.com cvs repository has its own versions of tcl,
expect, and dejagnu. I don't have the resources to test with both
tcl/expect/dejagnu stacks, so I choose the stock stack for my test
bed.
The sources.redhat.com version of tcl is nearly identical to tcl
8.4.1. The sources.redhat.com version of expect dates from
1998-06-15. The sources.redhat.com version of dejagnu is nearly
identical to dejagnu 1.4.3.
I have packaged and published my scripts to manage the baseline
software. They are called Migchain (Michael's Gnu Toolchain) and
Migbat (Michael's Gnu Build and Test), and they are licensed under the
GPL.
ftp://ftp.shout.net/pub/users/mec/migchain/migchain-0.8.tar.gz
ftp://ftp.shout.net/pub/users/mec/migbat/migbat-0.8.tar.gz
. Test Bed Changes Since Last Report
I added gdb 6.0.91.
I added gdb 6.1.