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: gdb-testers at sources dot redhat dot com
- Date: Wed, 9 Jun 2004 23:20:42 -0400 (EDT)
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
There is one new regression in gdb HEAD with gdb.threads/manythreads.exp
(pr gdb/1650).
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
not analyzed
gdb HEAD versus gdb 6.1
gdb/1444 gdb/1613 gdb/1650
gdb gdb_6_1-branch versus gdb 6.1
no improvements and no regressions
. Gcc Regression Summary
gcc HEAD versus gcc 3.4.0
gcc/13974 gcc/14048 gcc/14049 gcc/14860 gcc/15721
gdb/1656
gcc gcc-3_4-branch versus gcc 3.4.0
no improvements and no regressions
gcc 3.4.0 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
gcc 3.3.4-20040530 versus gcc 3.3.3
no improvements and no regressions
gcc 3.3.3 versus gcc 2.95.3
not analyzed
. Binutils Regression Summary
binutils HEAD versus binutils 2.15
binutils binutils_2-15-branch versus binutils 2.15
no improvements and no regressions
. Old Bugs Fixed Since Last Spin
. suite HEAD
http://sources.redhat.com/gdb/bugs/1636
manythreads.exp issues async ^C that spills onto next script
Michael C fixed it.
http://sources.redhat.com/gdb/bugs/1647
gdb.base/auxv.exp, incomplete input consumption
Roland M fixed it.
. New Bugs Detected Since Last Spin
. gdb HEAD
http://sources.redhat.com/gdb/bugs/1650
manythreads.exp
manythreads.exp already shows regressions from gdb 6.1 to gdb HEAD.
With this spin, there is an additional regression.
. PR Count
Query executed 2004-06-09 17:30:30 UTC
1665 matches found
21 analyzed
772 closed
23 feedback
829 open
3 paperwork
17 suspended
1665 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
gdb HEAD 745 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.15.
The binutils version should not make a difference.
. Gdb Testing
My tables are at
http://www.shout.net/~mec/sunday/2004-06-06/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-06-01/index.html
. Non-Pass Results
gdb 6.1
suite 6.1 1032 non-PASS results
suite HEAD 1060 non-PASS results
gdb gdb_6_1-banch
suite gdb_6_1-branch 1033 non-PASS results
suite HEAD 1057 non-PASS results
gdb HEAD
suite HEAD 1090 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 1044 non-PASS results
suite HEAD 1061 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.1
. suite 6.1
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
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/print-threads.exp: Hit kill breakpoint, 10 (slow with kill breakpoint)
blank -> PASS
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.
t0 t1 t2 t3 t4 t5
PASS 3 44 44 44 43 44
FAIL 41 0 0 0 1 0
. gdb 6.1
. suite HEAD
. gdb.base/auxv.exp: *
blank -> PASS
WARNING -> blank
FAIL -> PASS
UNSUPPORTED -> PASS
UNSUPPORTED -> FAIL
Roland M fixed the test script.
http://sources.redhat.com/gdb/bugs/1647
gdb.base/auxv.exp, incomplete input consumption
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. 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.
t0 t1 t2 t3 t4 t5
PASS 1 13 14 13 13 14
FAIL 13 1 0 1 1 0
. gdb gdb_6_1-branch
. suite gdb_6_1-branch
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 10 (slow with kill breakpoint)
PASS -> blank
Same analysis as gdb 6.1 suite 6.1.
. 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.
t0 t1 t2 t3 t4 t5
PASS 5 38 43 44 43 44
FAIL 39 6 1 0 1 0
. gdb gdb_6_1-branch
. suite HEAD
. gdb.base/auxv.exp: *
blank -> PASS
WARNING -> blank
FAIL -> PASS
UNSUPPORTED -> PASS
UNSUPPORTED -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. 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.
t0 t1 t2 t3 t4 t5
PASS 0 14 14 14 14 14
FAIL 14 0 0 0 0 0
. gdb HEAD
. suite HEAD
. gdb.base/auxv.exp: *
blank -> PASS
WARNING -> blank
FAIL -> PASS
UNSUPPORTED -> PASS
UNSUPPORTED -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
PASS -> FAIL
gdb.threads/manythreads.exp: stop threads 1
PASS -> FAIL
FAIL -> PASS
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
The regression in 'GDB exits after stopping multithreaded program'
is new in this spin.
. gdb.threads/print-threads.exp: *
* -> *
Michael C fixed a cascade bug in the preceding test script.
http://sources.redhat.com/gdb/bugs/1636
manythreads.exp issues async ^C that spills onto next script
. 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.
t0 t1 t2 t3 t4 t5
PASS 11 41 41 42 38 44
FAIL 33 3 3 2 6 0
. gdb drow_intercu-20040221-branch
. suite drow_intercu-20040221-branch
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
blank -> PASS
PASS -> blank
Same analysis as gdb 6.1 suite 6.1.
. 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.
t0 t1 t2 t3 t4 t5
PASS 6 7 12 12 11 14
FAIL 8 7 2 2 3 0
. gdb drow_intercu-20040221-branch
. suite HEAD
. gdb.base/auxv.exp: *
blank -> PASS
WARNING -> blank
FAIL -> PASS
UNSUPPORTED -> PASS
UNSUPPORTED -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.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
blank -> PASS
PASS -> blank
gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program (GDB internal error)
gdb.threads/manythreads.exp: stop threads 1 (GDB internal error)
gdb.threads/manythreads.exp: stop threads 2 (GDB internal error)
gdb.threads/manythreads.exp: stop threads 2 (timeout)
blank -> FAIL
FAIL -> blank
Same analysis as gdb HEAD suite HEAD.
. gdb.threads/print-threads.exp: *
* -> *
Same analysis as gdb HEAD suite HEAD.
. Package Versions
. This Spin
binutils HEAD 2004-06-05 03:35:21 UTC
binutils binutils-2_15-branch 2004-06-05 03:37:56 UTC
gcc HEAD 2004-06-05 03:44:17 UTC
gcc gcc-3_4-branch 2004-06-05 03:52:05 UTC
gcc gcc-3_3-branch 2004-06-05 04:00:24 UTC
gdb HEAD 2004-06-06 19:02:08 UTC
gdb drow_intercu-20040221-branch 2004-06-06 19:08:07 UTC
gdb gdb_6_1-branch 2004-06-06 19:11:05 UTC
. Last Spin
binutils HEAD 2004-05-31 02:13:57 UTC
binutils binutils-2_15-branch 2004-05-31 02:16:53 UTC
gcc HEAD 2004-05-31 02:21:04 UTC
gcc gcc-3_4-branch 2004-05-31 02:28:46 UTC
gcc gcc-3_3-branch 2004-05-31 02:36:26 UTC
gdb HEAD 2004-06-03 17:47:54 UTC
gdb drow_intercu-20040221-branch 2004-06-01 22:50:50 UTC
gdb gdb_6_1-branch 2004-06-03 02:10:47 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.1, gdb_6_1-branch, HEAD, drow_intercu-20040221-branch
suite => 6.1, gdb_6_1-branch, HEAD, drow_intercu-20040221-branch
cc => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.3, gcc 3.3.4-20040530, gcc gcc-3_3-branch, gcc 3.4.0, gcc gcc-3_4-branch, gcc HEAD
as => binutils 2.13.90.0.2-rh, binutils 2.15, binutils binutils-2_15-branch, binutils HEAD
ld => binutils 2.13.90.0.2-rh, binutils 2.15, binutils binutils-2_15-branch, binutils HEAD
libc => glibc 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count => 188
'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 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. I test other gdb/suite
configurations only with as binutils 2.15 + ld binutils 2.15.
. Host Software
. host=i686-pc-linux-gnu, osversion=red-hat-8.0
make 3.79.1
binutils 2.14
gcc 3.3.3
flex 2.5.4
bison 1.875
texinfo 4.7
tcl 8.4.6
expect 5.41
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 dropped gcc 3.3.4-20040517.