gdb, native i686-pc-linux-gnu
Michael Chastain
mec.gnu@mindspring.com
Tue Sep 28 17:10:00 GMT 2004
. Highlights of This Spin
I added gcc 3.3.5-20040918. It's healthy.
Daniel Jacobowitz did a big merge from gdb HEAD to gdb
drow_intercu-20040221-branch. Using the same test suite (suite HEAD),
the intercu branch has no results regressions compared to gdb HEAD.
This is the last spin for gdb gdb_6_2-branch.
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
no regressions
gdb HEAD versus gdb gdb_6_2-branch
gcore regression
http://sources.redhat.com/ml/gdb/2004-09/msg00202.html
gdb gdb_6_2-branch versus gdb 6.2.1
no improvements and no regressions
. Gcc Regression Summary
gcc HEAD versus gcc 3.4.2
gcc/13974
gdb/1656 gdb/1734 gdb/1742
gcc gcc-3_4-branch versus gcc 3.4.2
no improvements and no regressions
gcc 3.4.2 versus gcc 3.3.4
gcc/12267 gcc/13708
gdb/1537 gdb/1540
gcc gcc-3_3-branch versus gcc 3.3.4
gcc 3.3.5-20040918 versus gcc 3.3.4
gcc 3.3.5-20040914 versus gcc 3.3.4
no improvements and no regressions
gcc 3.3.4 versus gcc 2.95.3
not analyzed
. Binutils Regression Summary
binutils HEAD versus binutils 2.15
no improvements and no regressions
. Old Bugs Fixed Since Last Spin
None.
. New Bugs Detected Since Last Spin
. gdb HEAD
http://sources.redhat.com/ml/gdb/2004-09/msg00202.html
Regression in the gcore command.
This has already been fixed in gdb HEAD.
. PR Count
Query executed 2004-09-28 16:55:01 2004
1783 matches found
22 analyzed
842 closed
23 feedback
876 open
3 paperwork
17 suspended
1783 TOTAL
. Libiberty Testing
. target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
binutils HEAD 746 tests, 0 failures
gcc gcc-3_3-branch 649 tests, 0 failures
gcc gcc-3_4-branch 745 tests, 0 failures
gcc HEAD 746 tests, 0 failures
gdb HEAD 746 tests, 0 failures
gdb drow_intercu-20040221-branch 746 tests, 0 failures
gdb gdb_6_2-branch 746 tests, 0 failures
For gcc tests, the test results are with binutils 2.15.
The binutils version should not make a difference.
. Gdb Testing
My tables are at
http://www.shout.net/~mec/sunday/2004-09-22/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-09-15/index.html
. Non-Pass Results
suite 6.2.1
suite 6.2.1 1480 non-PASS results
suite HEAD 385 non-PASS results
gdb gdb_6_2-branch
suite gdb_6_2-branch 1483 non-PASS results
suite HEAD 384 non-PASS results
gdb HEAD
suite HEAD 383 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 377 non-PASS results
suite HEAD 375 non-PASS results
. gdb 6.2.1
. suite 6.2.1
. 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.threads/manythreads.exp: GDB exits after stopping multithreaded program
gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
FAIL -> FAIL
This is a bug in gdb. It happens intermittently.
http://sources.redhat.com/gdb/bugs/1650
manythreads.exp
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
PASS -> blank
Fluctuation with unknown cause. Probably harmless.
. gdb.threads/schedlock.exp: *
PASS
UNSUPPORTED
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 non-gcc-HEAD configurations except for
the "thread N ran" tests. Here are the counts per thread.
t0 t1 t2 t3 t4 t5
PASS 1 30 30 30 29 30
FAIL 29 0 0 0 1 0
. gdb 6.2.1
. suite HEAD
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.2.1 suite 6.2.1.
. gdb.java/jprint.exp: *
blank -> PASS
blank -> FAIL
blank -> UNTESTED
Jeff Johnston wrote a new test script.
. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
FAIL -> FAIL
Same analysis as gdb 6.2.1 suite 6.2.1.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
blank -> PASS
PASS -> blank
Same analysis as gdb 6.2.1 suite 6.2.1.
. 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.
t0 t1 t2 t3 t4 t5
PASS 4 11 15 15 15 16
FAIL 12 5 1 1 1 0
. gdb gdb_6_2-branch
. suite gdb_6_2-branch
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb 6.2.1 suite 6.2.1.
. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
FAIL -> FAIL
Same analysis as gdb 6.2.1 suite 6.2.1.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
PASS -> blank
Same analysis as gdb 6.2.1 suite 6.2.1.
. gdb.threads/schedlock.exp: *
PASS
UNSUPPORTED
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 non-gcc-HEAD configurations except for
the "thread N ran" tests. Here are the counts per thread.
t0 t1 t2 t3 t4 t5
PASS 2 27 29 30 30 30
FAIL 28 3 1 0 0 0
. gdb gdb_6_2-branch
. suite HEAD
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.2.1 suite 6.2.1.
. gdb.java/jprint.exp: *
blank -> PASS
blank -> FAIL
blank -> UNTESTED
Same analysis as gdb 6.2.1 suite HEAD.
. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
FAIL -> FAIL
Same analysis as gdb 6.2.1 suite 6.2.1.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
PASS -> blank
Same analysis as gdb 6.2.1 suite 6.2.1.
. 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.
t0 t1 t2 t3 t4 t5
PASS 6 11 15 15 16 16
FAIL 10 5 1 1 0 0
. gdb HEAD
. suite HEAD
. gdb.base/gcore.exp: where in corefile
gdb.base/gcore.exp: corefile restored stack array
gdb.base/gcore.exp: corefile restored backtrace
PASS -> FAIL
This happened with stabs+ with all versions of gcc 2 and gcc 3.
This is a bug in gdb:
http://sources.redhat.com/ml/gdb/2004-09/msg00202.html
The bug has already been fixed.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
. gdb.java/jprint.exp: *
blank -> UNTESTED
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.2.1 suite HEAD.
. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
FAIL -> FAIL
Same analysis as gdb 6.2.1 suite 6.2.1.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
PASS -> blank
Same analysis as gdb 6.2.1 suite 6.2.1.
. 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.
t0 t1 t2 t3 t4 t5
PASS 9 26 31 32 33 34
FAIL 25 8 3 2 1 0
. gdb drow_intercu-20040221-branch
The last change on this branch was 2004-09-21.
Daniel Jacobowitz did a big merge from HEAD.
. suite drow_intercu-20040221-branch
Not analyzed.
. suite HEAD
I compared the results from last spin to this spin. The merge
from gdb HEAD caused a lot of improvements. There were some PASS
-> KFAIL regressions in gdb.base/sigbpt.exp, but gdb HEAD also
has these KFAIL results.
More interesting is the comparison of gdb HEAD with
gdb drow_intercu-20040221-branch using the same test suite:
http://www.shout.net/~mec/sunday/2004-09-22/Compare-by-gdb-HEAD-drow.html
The gcore bug is in gdb HEAD but not the intercu branch. Other than
that, there are no significant result differences between gdb HEAD and
gdb drow_intercu_20040221-branch.
. Package Versions
. This Spin
binutils HEAD 2004-09-22 05:10:17 UTC
gcc HEAD 2004-09-22 05:22:40 UTC
gcc gcc-3_4-branch 2004-09-22 05:41:05 UTC
gcc gcc-3_3-branch 2004-09-22 05:59:49 UTC
gdb HEAD 2004-09-23 03:28:59 UTC
gdb drow_intercu-20040221-branch 2004-09-23 03:42:52 UTC
gdb gdb_6_2-branch 2004-09-23 03:49:39 UTC
. Last Spin
binutils HEAD 2004-09-14 11:17:30 UTC
gcc HEAD 2004-09-14 11:36:41 UTC
gcc gcc-3_4-branch 2004-09-14 11:52:23 UTC
gcc gcc-3_3-branch 2004-09-14 12:08:22 UTC
gdb HEAD 2004-09-15 17:18:53 UTC
gdb drow_intercu-20040221-branch 2004-09-15 17:30:48 UTC
gdb gdb_6_2-branch 2004-09-15 17:36:49 UTC
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
dejagnu => dejagnu 1.4.4
expect => expect 5.41
tcl => tcl 8.4.6
gdb => 6.2.1, gdb_6_2-branch, HEAD, drow_intercu-20040221-branch
suite => 6.2.1, gdb_6_2-branch, HEAD, drow_intercu-20040221-branch
cc => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.4, gcc 3.3.5-20040914, gcc 3.3.5-20040918, gcc gcc-3_3-branch, gcc 3.4.2, gcc gcc-3_4-branch, gcc HEAD
as => binutils 2.13.90.0.2-rh, binutils 2.15, binutils HEAD
ld => binutils 2.13.90.0.2-rh, binutils 2.15, binutils HEAD
libc => glibc 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count => 166
'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 tested gdb 6.2.1 suite 6.2.1, gdb gdb_6_2-branch suite
gdb_6-2-branch, and gdb HEAD suite HEAD with the full spectrum of as
and ld. I tested other gdb/suite configurations only with as binutils
2.15 + ld binutils 2.15.
. Test Bed Changes Since Last Report
I added gcc 3.3.5-20040918.
This is the last spin for gcc 3.3.5-20040914.
This is the last spin for gdb gdb_6_2-branch.
More information about the Gcc-testresults
mailing list