This is the mail archive of the
gcc-testresults@gcc.gnu.org
mailing list for the GCC 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: Fri, 7 May 2004 04:31:41 -0400 (EDT)
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
It's been 17 days since the last spin.
gdb has some new tests which reveal some regressions in gdb HEAD
versus gdb 6.1.
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
gdb.arch/i386-prologue.exp: check jump_at_beginning prologue end
gdb.base/call-sc.exp: return foo; return call-sc-tld
gdb.base/call-sc.exp: value foo returned; return call-sc-td
gdb.base/call-sc.exp: value foo returned; return call-sc-tf
gdb.base/call-sc.exp: value foo returned; return call-sc-tld
gdb.threads/manythreads.exp: stop threads 1 (GDB internal error)
gdb.threads/manythreads.exp: stop threads 2 (GDB internal error)
gdb HEAD versus gdb 6.1
gdb/1613
gdb.threads/manythreads.exp: stop threads 1 (GDB internal error)
gdb.threads/manythreads.exp: stop threads 2 (GDB internal error)
gdb gdb_6_1-branch versus gdb 6.1
no improvements and no regressions
. Gcc Regression Summary
gcc tree-ssa-20020619-branch versus gcc HEAD
gcc/14048 gcc/14049
gcc HEAD versus gcc 3.4.0
gcc/13974 gcc/14860
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
no improvements and no regressions
gcc 3.3.3 versus gcc 2.95.3
not analyzed
. Binutils Regression Summary
binutils HEAD versus binutils 2.14
binutils binutils-2_15-branch versus binutils 2.14
binutils 2.14.91 versus binutils 2.14
gdb/1470
gdb no longer has PLT entries for shared library functions
gdb asks if the user wants to set a pending breakpoint
the test script shlib-call.exp needs an update
binutils is okay
. Old Bugs Fixed Since Last Spin
None.
. New Bugs Detected Since Last Spin
. suite HEAD
http://sources.redhat.com/gdb/bugs/1636
manythreads.exp issues async ^C that spills onto next script
. PR Count
Query executed 2004-05-07 00:51:38 UTC
1635 matches found
21 analyzed
759 closed
23 feedback
813 open
3 paperwork
16 suspended
1635 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
gcc tree-ssa-20020619-branch 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.14.
The binutils version should not make a difference.
. Gdb Testing
My tables are at
http://www.shout.net/~mec/sunday/2004-05-03/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-04-16/index.html
. Non-Pass Results
gdb 6.1
suite 6.1 1032 non-PASS results
suite HEAD 1061 non-PASS results
gdb gdb_6_1-banch
suite gdb_6_1-branch 1032 non-PASS results
suite HEAD 1061 non-PASS results
gdb HEAD
suite HEAD 1083 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 1041 non-PASS results
suite HEAD 1046 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.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.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 57 55 57 57 58
FAIL 53 1 3 1 1 0
. gdb 6.1
. suite HEAD
. gdb.arch/i386-prologue.exp: check jump_at_beginning prologue end
blank -> FAIL
Jerome G added a new test.
. 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
Same analysis as gdb 6.1 suite 6.1.
. gdb.base/call-sc.exp: *
blank -> PASS
blank -> FAIL
Andrew C added a new test script, with some additional
work by Mark K.
. gdb.base/siginfo.exp: step out of handler
FAIL -> KFAIL
Andrew C improved the test script.
. gdb.base/sigstep.exp: *
blank -> PASS
blank -> KFAIL
Andrew C wrote a new test script.
. gdb.stabs/exclfwd.exp: *
blank -> PASS
blank -> FAIL
blank -> KFAIL
Jim B wrote a new test script.
. gdb.threads/manythreads.exp: *
blank -> PASS
Jeff J and Daniel J wrote a new test 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 2 13 14 14 13 14
FAIL 12 1 0 0 1 0
. gdb gdb_6_1-branch
. suite gdb_6_1-branch
. 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.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
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 9 52 53 56 55 58
FAIL 49 6 5 2 3 0
. gdb gdb_6_1-branch
. suite HEAD
. gdb.arch/i386-prologue.exp: check jump_at_beginning prologue end
blank -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. 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
Same analysis as gdb 6.1 suite 6.1.
. gdb.base/call-sc.exp: *
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/siginfo.exp: step out of handler
FAIL -> KFAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/sigstep.exp: *
blank -> PASS
blank -> KFAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb gdb_6_1-branch suite gdb_6_1-branch.
. gdb.stabs/exclfwd.exp: *
blank -> PASS
blank -> FAIL
blank -> KFAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.threads/manythreads.exp: *
blank -> PASS
Same analysis as gdb 6.1 suite 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 2 14 14 13 13 14
FAIL 12 0 0 1 1 0
. gdb HEAD
. suite HEAD
. gdb.arch/i386-prologue.exp: check jump_at_beginning prologue end
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. 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
Same analysis as gdb 6.1 suite 6.1.
. gdb.base/call-sc.exp: *
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/siginfo.exp: step out of handler
FAIL -> PASS
Andrew C improved the test script.
Someone might have improved gdb, also.
. gdb.base/sigstep.exp: *
blank -> PASS
blank -> KFAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb gdb_6_1-branch suite gdb_6_1-branch.
. gdb.stabs/exclfwd.exp: *
blank -> PASS
blank -> FAIL
blank -> KFAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.stabs/weird.exp: weirdx.o read without error
blank -> PASS
gdb.stabs/weird.exp: Errors reading weirdx.o
FAIL -> blank
Michael C improved the test script.
. gdb.threads/manythreads.exp: *
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.threads/print-threads.exp: *
blank -> ERROR
blank -> FAIL
blank -> UNRESOLVED
PASS -> blank
PASS -> FAIL
PASS -> UNRESOLVED
KFAIL -> blank
This is a cascade problem from the previous test script,
gdb.threads/manythreads.exp.
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 5 54 58 58 55 58
FAIL 53 4 0 0 3 0
. gdb drow_intercu-20040221-branch
. suite drow_intercu-20040221-branch
. 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
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb gdb_6_1-branch suite gdb_6_1-branch.
. 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 7 7 12 13 13 14
FAIL 7 7 2 1 1 0
. gdb drow_intercu-20040221-branch
. suite HEAD
. gdb.arch/i386-prologue.exp: check jump_at_beginning prologue end
blank -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. 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
Same analysis as gdb 6.1 suite 6.1.
. gdb.base/call-sc.exp: *
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/siginfo.exp: step out of handler
FAIL -> PASS
Same analysis as gdb HEAD suite HEAD.
. gdb.base/sigstep.exp: *
blank -> PASS
blank -> KFAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb gdb_6_1-branch suite gdb_6_1-branch.
. gdb.stabs/exclfwd.exp: *
blank -> PASS
blank -> FAIL
blank -> KFAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.threads/manythreads.exp: *
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.threads/print-threads.exp: *
blank -> ERROR
blank -> FAIL
blank -> UNRESOLVED
PASS -> blank
PASS -> FAIL
PASS -> UNRESOLVED
KFAIL -> blank
This is a cascade problem from the previous test script,
gdb.threads/manythreads.exp.
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 3 12 14 14 12 14
FAIL 11 2 0 0 2 0
. Package Versions
. This Spin
binutils HEAD 2004-05-01 10:31:18 UTC
binutils binutils-2_15-branch 2004-05-01 10:33:30 UTC
gcc tree-ssa-20020619-branch 2004-05-01 10:48:41 UTC
gcc HEAD 2004-05-01 10:56:51 UTC
gcc gcc-3_4-branch 2004-05-01 11:03:34 UTC
gcc gcc-3_3-branch 2004-05-01 11:11:25 UTC
gdb HEAD 2004-05-03 13:01:38 UTC
gdb drow_intercu-20040221-branch 2004-05-03 13:08:00 UTC
gdb gdb_6_1-branch 2004-05-03 13:10:15 UTC
. Last Spin
binutils HEAD 2004-04-14 19:49:00 UTC
binutils binutils-2_15-branch 2004-04-14 19:52:26 UTC
gcc tree-ssa-20020619-branch 2004-04-14 19:58:46 UTC
gcc HEAD 2004-04-14 20:11:53 UTC
gcc gcc-3_4-branch 2004-04-14 20:28:55 UTC
gcc gcc-3_3-branch 2004-04-14 20:37:03 UTC
gdb HEAD 2004-04-17 01:07:06 UTC
gdb drow_intercu-20040221-branch 2004-04-17 01:11:37 UTC
gdb gdb_6_1-branch 2004-04-17 01:15:19 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 gcc-3_3-branch, gcc 3.4.0, gcc gcc-3_4-branch, gcc HEAD, gcc tree-ssa-20020619-branch
as => binutils 2.13.90.0.2-rh, binutils 2.14, binutils 2.14.91, binutils binutils-2_15-branch, binutils HEAD
ld => binutils 2.13.90.0.2-rh, binutils 2.14, binutils 2.14.91, binutils binutils-2_15-branch, binutils HEAD
libc => glibc 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count => 230
'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.14 and ld binutils
2.14.
. Host Software
. host=i686-pc-linux-gnu, osversion=red-hat-8.0
make 3.79.1
binutils 2.14
gcc 3.3.2
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 6.0.
I upgraded host gcc from gcc 3.3.2 to gcc 3.3.3. This is the compiler
that I use to build gdb itself, not the compiler that I use to build
test programs for gdb.
I upgraded tcl from tcl 8.4.5 to tcl 8.4.6.
I upgraded expect from expect 5.39 to expect 5.41.