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: Sat, 30 Oct 2004 21:06:33 -0400
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
I added gdb 6.2.90 and gdb gdb_6_3-branch. They are both healthy.
gdb.threads/watchthreads.exp is an unstable test, which probably means
bugs in gdb. The bad results occur with all versions of gdb so it's
not a regression. I will dig into this later.
My current tables are always at
http://www.shout.net/~mec/sunday/current/index.html
. Gdb Regression Summary
gdb HEAD versus gdb 6.2.90
No improvements and no regressions.
gdb gdb-6_3-branch versus gdb 6.2.1
gdb 6.2.90 versus gdb 6.2.1
Several improvements and no regressions.
. Gcc Regression Summary
gcc HEAD versus gcc 3.4.2
gdb/1656 gdb/1734
gdb.mi/mi-until.exp: until after while loop
gdb.mi/mi2-until.exp: until after while loop
gcc gcc-3_4-branch versus gcc 3.4.2
no improvements and no regressions
gcc 3.4.2 versus gcc 3.3.5
gcc/12267 gcc/13708
gdb/1537 gdb/1540
gcc gcc-3_3-branch versus gcc 3.3.5
no improvements and no regressions
gcc 3.3.5 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
None.
. PR Count
Query executed 2004-10-30 17:56:55 UTC
1802 matches found
21 analyzed
863 closed
20 feedback
878 open
3 paperwork
17 suspended
1802 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 gdb_6_3-branch 746 tests, 0 failures
gdb HEAD 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-10-26/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-10-15/index.html
. Non-Pass Results
suite 6.2.1
suite 6.2.1 1479 non-PASS results
suite HEAD 377 non-PASS results
gdb 6.2.90
suite 6.2.90 408 non-PASS results
suite HEAD 406 non-PASS results
gdb gdb_6_3-branch
suite gdb_6_3-branch 410 non-PASS results
suite HEAD 405 non-PASS results
gdb HEAD
suite HEAD 411 non-PASS results
. gdb 6.2.1
. suite 6.2.1
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
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)
blank -> PASS
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 22 21 22 22 22
FAIL 21 0 1 0 0 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.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 5 6 9 12 12 12
FAIL 7 6 3 0 0 0
. gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
. gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
gdb.threads/watchthreads.exp: watchpoint on args[0] hit in thread
gdb.threads/watchthreads.exp: watchpoint on args[1] hit in thread
PASS -> FAIL
FAIL -> PASS
Not analyzed.
. gdb 6.2.90
This is the first spin for gdb 6.2.90.
. suite 6.2.90
Not analyzed.
. suite HEAD
I compared gdb 6.2.90 suite HEAD with gdb 6.2.1 suite HEAD.
There were several improvements and no regressions.
. gdb gdb_6_3-branch
This is the first spin for gdb gdb_6_3-branch.
. suite gdb_6_3-branch
Not analyzed.
. suite HEAD
I compared gdb gdb_6_3-branch suite HEAD with gdb 6.2.90 suite HEAD.
There were no significant differences.
. gdb HEAD
. suite HEAD
. gdb.ada/null_record.exp: start
PASS -> FAIL
Joel Brobecker improved the test script.
. 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.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 30 35 34 35 36
FAIL 32 6 1 2 1 0
. gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
gdb.threads/watchthreads.exp: watchpoint on args[0] hit in thread
gdb.threads/watchthreads.exp: watchpoint on args[1] hit in thread
PASS -> FAIL
FAIL -> PASS
Not analyzed.
. Package Versions
. This Spin
binutils HEAD 2004-10-21 15:25:00 UTC
gcc HEAD 2004-10-21 15:50:04 UTC
gcc gcc-3_4-branch 2004-10-21 16:04:03 UTC
gcc gcc-3_3-branch 2004-10-21 16:17:55 UTC
gdb gdb_6_3-branch 2004-10-26 10:21:20 UTC
gdb HEAD 2004-10-26 10:09:14 UTC
. Last Spin
binutils HEAD 2004-10-14 12:18:38 UTC
gcc HEAD 2004-10-14 12:38:16 UTC
gcc gcc-3_4-branch 2004-10-14 12:53:24 UTC
gcc gcc-3_3-branch 2004-10-14 13:10:50 UTC
gdb HEAD 2004-10-15 17:24:13 UTC
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
dejagnu => dejagnu 1.4.4
expect => expect 5.42
tcl => tcl 8.4.7
gdb => 6.2.1, HEAD
suite => 6.2.1, HEAD
cc => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.5, 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
ed2dup => no, yes
count => 180
'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 6.2.90 suite 6.2.90, gdb
gdb_6_3-branch suite gdb_6_3-branch, 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.
I tested with ed2dup=yes (-feliminate-dwarf2-dup) with these
configurations: dwarf-2, gcc 3.3 or later, gdb 6.2.90 or later.
. Host Software
. host=i686-pc-linux-gnu, osversion=red-hat-8.0
make 3.79.1
binutils 2.15
gcc 3.3.5
flex 2.5.4
bison 1.875
texinfo 4.7
tcl 8.4.7
expect 5.42
dejagnu 1.4.4
This is the software I use to build gdb and run the test suite. But
it is not the toolchain I use to build the test programs that run
under gdb.
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-1.0-pre-20041022.tar.bz2
ftp://ftp.shout.net/pub/users/mec/migbat/migbat-1.0-pre-20041022.tar.bz2
. Test Bed Changes Since Last Report
I added gdb 6.2.90.
I added gdb gdb_6_3-branch.
I upgraded the host software in my test bed:
gcc 3.3.4 -> gcc 3.3.5
tcl 8.4.6 -> tcl 8.4.7
expect 5.41 -> expect 5.42
The test bed uses the host gcc to build gdb and then uses several
different target gcc's to build the test programs. The tests in
gdb.gdb/*.exp are sensitive to the host gcc because they use gdb
itself as the target program, but all other tests are not sensitive
to the host gcc.