This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
gdb, native i686-pc-linux-gnu
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: binutils at sources dot redhat dot com, gcc-testresults at gcc dot gnu dot org,gdb-testers at sources dot redhat dot com
- Date: Wed, 21 Apr 2004 17:38:51 -0400 (EDT)
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
I added binutils 2.14.91 snapshot. It's healthy, with no regressions
from binutils 2.14 to binutils 2.14.91.
I added gcc 3.4.0. From gcc 3.3.3 to gcc 3.4.0, there are five
regressions (three belong to gcc; two belong to gdb).
This is the last spin for gdb 6.0. From gdb 6.0 to gdb 6.1
there were five regressions.
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.1
no improvements and no regressions
gdb gdb_6_1-branch versus gdb 6.1
no improvements and no regressions
gdb 6.1 versus gdb 6.0
gdb/931 gdb/1505 gdb/1512 gdb/1516 gdb/1588
. 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
. gcc gcc-3_4-branch
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14893
[3.4 Regression] 3.4.0-20040406, 'make install' fails on doc/gcjh.1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14905
'make install' fails on grepjar.1, not included in tarball
. New Bugs Detected Since Last Spin
None.
. PR Count
Query executed 2004-04-21 18:16:51 UTC
1617 matches found
22 analyzed
748 closed
24 feedback
804 open
3 paperwork
16 suspended
1617 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-04-16/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-04-09/index.html
. Non-Pass Results
gdb 6.0
suite 6.0 1117 non-PASS results
suite HEAD 1227 non-PASS results
gdb 6.1
suite 6.1 1031 non-PASS results
suite HEAD 1044 non-PASS results
gdb gdb_6_1-banch
suite gdb_6_1-branch 1032 non-PASS results
suite HEAD 1042 non-PASS results
gdb HEAD
suite HEAD 1049 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 1041 non-PASS results
suite HEAD 1041 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.0
. suite 6.0
. 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.mi/mi*-pthreads.exp: check mi_thread_command_set: -thread-select [3456]
blank -> PASS
PASS -> blank
When gdb operates on an inferior program with threads, gdb uses
hidden breakpoints in the thread library to track events such as
thread creation and thread destruction.
This causes some programs to behave differently because they
aren't prepared to handle the additional signals caused by the
hidden breakpoints. The test program for mi*-pthreads.exp is
such a program.
http://sources.redhat.com/ml/gdb/2003-09/msg00279.html
http://sources.redhat.com/gdb/bugs/259
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (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 8 54 56 57 55 58
FAIL 50 4 2 1 3 8
. gdb 6.0
. suite HEAD
. gdb.base/freebpcmd.exp: run program with breakpoint commands
KFAIL -> KFAIL
This is a non-deterministic memory corruption bug in gdb 6.0.
It has been fixed in gdb HEAD.
http://sources.redhat.com/gdb/bugs/1489
GDB crashes executing breakpoint commands that continue the inferior
. gdb.base/sep.exp: *
blank -> PASS
blank -> KFAIL
Joel B wrote a new test script.
. gdb.base/siginfo.exp: *
blank -> PASS
blank -> FAIL
Andrew C 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 1 14 14 14 14 14
FAIL 13 0 0 0 0 0
. gdb 6.1
. suite 6.1
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. 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 56 56 58 55 58
FAIL 52 2 2 0 3 0
. gdb 6.1
. suite HEAD
. gdb.base/sep.exp: *
blank -> PASS
blank -> KFAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/siginfo.exp: *
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. 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 4 12 13 13 13 14
FAIL 10 2 1 1 1 4
. gdb gdb_6_1-branch
. suite gdb_6_1-branch
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. 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 52 57 57 54 58
FAIL 52 6 1 1 4 0
. gdb gdb_6_1-branch
. suite HEAD
. gdb.base/sep.exp: *
blank -> PASS
blank -> KFAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/siginfo.exp: *
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 10 (slow with kill breakpoint)
blank -> PASS
Same analysis as gdb 6.0 suite 6.0.
. 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 HEAD
. suite HEAD
. gdb.base/sep.exp: *
blank -> PASS
blank -> KFAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/siginfo.exp: *
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.stabs/weird.exp: weirdx.o read without error
PASS -> blank
gdb.stabs/weird.exp: Errors reading weirdx.o
blank -> FAIL
This is a simple deficiency in the test script.
gdb changed its output and the test script needs an update.
# gdb.log, previous
(gdb) file object.o
Reading symbols from object.o...done.
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) PASS: gdb.stabs/weird.exp: weirdx.o read without error
# gdb.log, current
(gdb) file object.o
Reading symbols from /tmp/migbat-testgdb-n7isztC0/test/object.o...done.
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) FAIL: gdb.stabs/weird.exp: Errors reading weirdx.o
. 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.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
PASS -> blank
Same analysis as gdb 6.0 suite 6.0.
. 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 11 12 12 12 14
FAIL 8 3 2 2 2 0
. gdb drow_intercu-20040221-branch
. suite HEAD
. gdb.base/sep.exp: *
blank -> PASS
blank -> KFAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/siginfo.exp: *
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. 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 14 14
FAIL 11 2 0 0 0 0
. Package Versions
. This 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
. Last Spin
binutils HEAD 2004-04-07 04:26:24 UTC
binutils binutils-2_15-branch 2004-04-07 04:35:04 UTC
gcc tree-ssa-20020619-branch 2004-04-08 17:31:19 UTC
gcc HEAD 2004-04-08 17:38:50 UTC
gcc gcc-3_4-branch 2004-04-07 07:42:30 UTC
gcc gcc-3_3-branch 2004-04-07 09:26:11 UTC
gdb HEAD 2004-04-09 07:38:11 UTC
gdb drow-cplus-branch 2004-04-09 07:40:24 UTC
gdb drow_intercu-20040221-branch 2004-04-09 07:42:32 UTC
gdb gdb_6_1-branch 2004-04-09 07:44:43 UTC
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
dejagnu => dejagnu 1.4.4
expect => expect 5.39
tcl => tcl 8.4.5
gdb => 6.0, 6.1, gdb_6_1-branch, HEAD, drow_intercu-20040221-branch
suite => 6.0, 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 => 236
'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.0 suite 6.0, 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
tcl 8.4.5
expect 5.39
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 added binutils 2.14.91.
I added gcc 3.4.0.
I dropped gdb drow-cplus-branch. I will cover this branch again if
there is activity on the branch.
I enhanced the "compare by ..." tables. Instead of "compare by gdb",
which compares all versions of gdb, I produce several pair-wise
tables: gdb 6.0 versus gdb 6.1; gdb 6.1 versus gdb_6_1-branch; gdb 6.1
versus gdb HEAD; gdb HEAD versus gdb drow.* . This makes it easier to
extract useful information from the megabytes of raw results.
I made similar pair-wise tables for gcc.
I replaced the useless tables "compare by as" and "compare by ld"
with a useful "compare by as-ld" table.
I made some other minor improvements to the difference tables.