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: Sat, 17 Jul 2004 21:48:28 -0400 (EDT)
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
I added gdb gdb-6_2-branch. There are no significant differences
from gdb HEAD to gdb gdb_6-2-branch.
There was one bug detected with gcj line numbers, but it's an old bug
detected by a new test.
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 gdb_6_2-branch
no improvements and no regressions
gdb gdb_6_2-branch versus gdb 6.1.1
gdb/1650
. Gcc Regression Summary
gcc HEAD versus gcc 3.4.1
gcc/13974 gcc/14049 gcc/14860
gdb/1656
gcc gcc-3_4-branch versus gcc 3.4.1
no improvements and no regressions
gcc 3.4.1 versus gcc 3.3.4
gcc/12267 gcc/13708 gcc/13956
gdb/1537 gdb/1540
gcc gcc-3_3-branch 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
. gcc HEAD
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16439
gcj doesn't generate proper debugging line number info
This is a new detection of an existing bug.
The bug happened with gcc 3.3.4, gcc 3.4.1, and gcc HEAD.
. PR Count
Query executed 2004-07-18 01:07:44 UTC
1713 matches found
22 analyzed
781 closed
23 feedback
867 open
3 paperwork
17 suspended
1713 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 745 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-07-15/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-07-08/index.html
. Non-Pass Results
gdb 6.1.1
suite 6.1.1 995 non-PASS results
suite HEAD 971 non-PASS results
gdb gdb_6_2-banch
suite gdb_6_2-branch 970 non-PASS results
suite HEAD 965 non-PASS results
gdb HEAD
suite HEAD 968 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 1006 non-PASS results
suite HEAD 974 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.1
. suite 6.1.1
. gdb.base/bigcore.exp: extract next heap
gdb.base/bigcore.exp: extract prev heap
blank -> PASS
gdb.base/bigcore.exp: extract next heap (stop at 50)
gdb.base/bigcore.exp: extract prev heap (stop at 50)
PASS -> blank
Not analyzed. Probably harmless.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
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/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 2 25 26 25 25 26
FAIL 24 1 0 1 1 0
. gdb 6.1.1
. suite HEAD
. gdb.base/annota1.exp: *
gdb.base/annota3.exp: *
gdb.base/attach.exp: *
gdb.base/ena-dis-br.exp: *
gdb.base/signull.exp: *
gdb.base/sizeof.exp *
gdb.gdb/observer.exp: *
blank -> PASS
PASS -> blank
gdb.base/ena-dis-br.exp: continue with ignore count, not stopped at bpt
XFAIL -> KFAIL
Andrew Cagney improved the test names and did other
cleanups in the test scripts.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.1.1 suite 6.1.1.
. gdb.java/jmain.exp: break 'jmain.main(java.lang.String[])'
PASS -> XFAIL
FAIL -> XFAIL
Jeff Johnston improved the test script to specify the
expected line number when stopping at a breakpoint.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16439
gcj doesn't generate proper debugging line number info
The bug happened with gcc 3.3.4, gcc 3.4.1, and gcc HEAD.
. 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 11 12 12 12 12
FAIL 11 1 0 0 0 0
. gdb gdb_6_2-branch
. suite gdb_6_2-branch
This is the first spin for gdb gdb_6_2-branch.
I did not analyze the results for gdb gdb_6_2-branch suite
gdb_6_2-branch.
. suite HEAD
This is the first spin for gdb gdb_6_2-branch.
I compared gdb gdb_6_2-branch suite HEAD with gdb HEAD suite HEAD.
There were no significant differences.
. gdb HEAD
. suite HEAD
. gdb.base/annota1.exp: *
gdb.base/annota3.exp: *
gdb.base/attach.exp: *
gdb.base/ena-dis-br.exp: *
gdb.base/signull.exp: *
gdb.base/sizeof.exp *
gdb.gdb/observer.exp: *
blank -> PASS
PASS -> blank
gdb.base/ena-dis-br.exp: continue with ignore count, not stopped at bpt
XFAIL -> KFAIL
Same analysis as gdb 6.1.1 suite HEAD.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
Same analysis as gdb 6.1.1 suite 6.1.1.
. gdb.java/jmain.exp: break 'jmain.main(java.lang.String[])'
PASS -> XFAIL
FAIL -> XFAIL
Same analysis as gdb 6.1.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
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
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 25 26 26 24 26
FAIL 21 1 0 0 2 0
. gdb drow_intercu-20040221-branch
. suite drow_intercu-20040221-branch
The last change on this branch was 2004-04-19.
I examined the tables and nothing noteworthy.
. suite HEAD
There was one noteworthy change:
. gdb.threads/pthread_cond_wait.exp: backtrace in blocked thread
PASS -> FAIL
This happened with gcc HEAD -gstabs+.
In the last spin, this configuration had a transient problem.
The problem disappeared with this spin.
. Package Versions
. Package Versions
. This Spin
binutils HEAD 2004-07-14 08:03:49 UTC
gcc HEAD 2004-07-14 08:18:08 UTC
gcc gcc-3_4-branch 2004-07-14 08:37:13 UTC
gcc gcc-3_3-branch 2004-07-14 08:53:05 UTC
gdb HEAD 2004-07-15 01:39:42 UTC
gdb drow_intercu-20040221-branch 2004-07-15 01:53:29 UTC
gdb gdb_6_2-branch 2004-07-15 02:00:17 UTC
. Last Spin
binutils HEAD 2004-06-17 18:55:08 UTC
binutils binutils-2_15-branch 2004-06-17 18:58:51 UTC
gcc HEAD 2004-06-17 19:02:54 UTC
gcc gcc-3_4-branch 2004-06-17 19:11:35 UTC
gcc gcc-3_3-branch 2004-06-17 19:20:18 UTC
gdb HEAD 2004-06-19 07:27:27 UTC
gdb drow_intercu-20040221-branch 2004-06-19 07:35:36 UTC
gdb gdb_6_1-branch 2004-06-19 07:39:10 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.1, gdb_6_2-branch, HEAD, drow_intercu-20040221-branch
suite => 6.1.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 gcc-3_3-branch, gcc 3.4.1, 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 => 126
'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 gdb 6.1.1 suite 6.1.1, gdb_6_2-branch suite gdb_6-2-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 gdb gdb_6_1-branch.
I added gdb gdb_6-2-branch.
I dropped gcc 3.3.3.
I dropped gcc 3.3.4-20040530.
I dropped gcc 3.4.0.
I dropped gcc 3.4.1-20040625.
I dropped binutils binutils-2_15-branch.