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: Michael Chastain <mec dot gnu at mindspring dot com>
- To: gcc-testresults at gcc dot gnu dot org, gdb-testers at sources dot redhat dot com
- Date: Fri, 08 Oct 2004 10:11:31 -0400
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
No new regressions this spin.
I dropped 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 improvements and no regressions
gdb HEAD versus gdb 6.2.1
several 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
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
. gdb HEAD
http://sources.redhat.com/ml/gdb/2004-09/msg00202.html
Alan Modra fixed a bfd regression in gdb.
. New Bugs Detected Since Last Spin
None.
. PR Count
Query executed 2004-10-01 14:58:38 2004
1784 matches found
22 analyzed
842 closed
23 feedback
877 open
3 paperwork
17 suspended
1784 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
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-29/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-09-22/index.html
. Non-Pass Results
suite 6.2.1
suite 6.2.1 1480 non-PASS results
suite HEAD 386 non-PASS results
gdb HEAD
suite HEAD 381 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 377 non-PASS results
suite HEAD 376 non-PASS results
. 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
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)
blank -> PASS
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 26 26 26 24 26
FAIL 24 0 0 0 2 0
. gdb 6.2.1
. suite HEAD
. gdb.base/bigcore.exp: *
blank -> PASS
blank -> FAIL
PASS -> blank
XFAIL -> blank
Andrew Cagney and David Anderson improved the test script
and the test program.
. gdb.base/constvars.exp: ptype crass
gdb.base/constvars.exp: ptype qux1
gdb.base/volatile.exp: ptype qux2
FAIL -> XFAIL
This happened with gcc HEAD -gstabs+.
Michael Chastain improved the test scripts to accept gcc 4.
. 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/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/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 10 13 14 14 14
FAIL 10 4 1 0 0 0
. gdb HEAD
. suite HEAD
. gdb.base/bigcore.exp: *
gdb.base/constvars.exp: ptype crass
gdb.base/constvars.exp: ptype qux1
gdb.base/volatile.exp: ptype qux2
*
Same analysis as gdb 6.2.1 suite HEAD.
. gdb.base/gcore.exp: where in corefile
gdb.base/gcore.exp: corefile restored stack array
gdb.base/gcore.exp: corefile restored backtrace
FAIL -> PASS
Alan Modra fixed a bfd regression in gdb.
http://sources.redhat.com/ml/gdb/2004-09/msg00202.html
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
FAIL -> PASS
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)
blank -> PASS
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 10 23 28 27 28 30
FAIL 20 7 2 3 2 0
. gdb drow_intercu-20040221-branch
The last change on this branch was 2004-09-21.
. suite drow_intercu-20040221-branch
I examined the tables and found nothing noteworthy.
. suite HEAD
I examined the tables and found nothing noteworthy.
. Package Versions
. This Spin
binutils HEAD 2004-09-28 17:09:39 UTC
gcc HEAD 2004-09-28 17:25:19 UTC
gcc gcc-3_4-branch 2004-09-28 17:41:56 UTC
gcc gcc-3_3-branch 2004-09-28 17:58:33 UTC
gdb HEAD 2004-09-29 13:58:01 UTC
gdb drow_intercu-20040221-branch 2004-09-29 14:12:55 UTC
. Last 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
. 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, HEAD, drow_intercu-20040221-branch
suite => 6.2.1, HEAD, drow_intercu-20040221-branch
cc => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.4, 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 => 102
'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 and gdb HEAD suite HEAD with the full
spectrum of as and ld. I tested other gdb/suite configurations with
just as binutils 2.15 + ld binutils 2.15.
. Test Bed Changes Since Last Report
I dropped gcc 3.3.5-20040914.
I dropped gdb gdb_6_2-branch.
I adjusted my test bed to handle a glitch in gdb.base/bigcore.c.
bigcore.c creates a zero-length file "bigcore.corefile" with
an uninitialized (random) mode.