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: Wed, 10 Mar 2004 13:04:29 -0500 (EST)
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
There were no significant changes in this spin.
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.cp/namespace.exp: ptype CClass::NestedClass
this is worse
gdb.cp/templates.exp: ptype Baz
this is better, but it's probably accidental
gdb.mi/mi*-var-display.exp: *
this is better
gdb HEAD versus gdb 6.0
gdb/826 gdb/931 gdb/1505 gdb/1512 gdb/1516
gdb gdb_6_1-branch versus gdb 6.0
gdb/826 gdb/931 gdb/1505 gdb/1512 gdb/1516
. Gcc Regression Summary
gcc tree-ssa-20020619-branch versus gcc HEAD
gcc/14048 gcc/14049
gcc HEAD versus gcc 3.3.3
gcc/12267 gcc/13708 gcc/13956 gcc/13974
gdb/1537 gdb/1540
classes.exp unanalyzed regressions
gcc gcc-3_4-branch versus gcc 3.3.3
gcc/12267 gcc/13708 gcc/13956 gcc/13974
gdb/1537 gdb/1540
classes.exp unanalyzed regressions
gcc gcc-3_3-branch versus gcc 3.3.3
no improvements and no regressions
. Binutils Regression Summary
binutils HEAD versus binutils 2.14
binutils binutils-2_15-branch versus binutils 2.14
gdb.base/gdb1250.exp unanalyzed regressions
gdb.base/gdb1476.exp unanalyzed regressions
gdb.base/shlib-call.exp unanalyzed regressions
. Old Bugs Fixed Since Last Spin
None.
. New Bugs Detected Since Last Spin
None.
. PR Count
Query executed 2004-03-10 16:20:15 UTC
1583 matches found
22 analyzed
740 closed
25 feedback
777 open
3 paperwork
16 suspended
1583 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-cplus-branch 742 tests, 0 failures
gdb drow_intercu-20040221-branch 742 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-03-08/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-03-02/index.html
. Non-Pass Results
gdb 6.0
suite 6.0 459 non-PASS results
suite HEAD 622 non-PASS results
gdb gdb_6_1-banch
suite gdb_6_1-branch 464 non-PASS results
suite HEAD 453 non-PASS results
gdb HEAD
suite HEAD 464 non-PASS results
gdb drow-cplus-branch
suite drow-cplus-branch 613 non-PASS results
suite HEAD 625 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 440 non-PASS results
suite HEAD 472 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.base/break.exp: *
ERROR -> blank
FAIL -> PASS
FAIL -> FAIL
UNRESOLVED -> PASS
This happened with gcc tree-ssa-20020619-branch -gdwarf-2.
It looks like this particular test program no longer has
a dwarf-2 location list in the executable.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> 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.cp/templates.exp: ptype quxint
PASS -> FAIL
This happened with gcc tree-ssa-20020619-branch -gdwarf-2.
Here are gdb.log excerpts:
# Last Spin
ptype quxint
type = class Qux<int,&string> {
public:
int x;
int t;
int qux(int, int);
}
(gdb) PASS: gdb.cp/templates.exp: ptype quxint
# This Spin
(gdb) PASS: gdb.cp/templates.exp: ptype Qux
ptype quxint
type = class Qux<int,(char*)(&string)> {
public:
int x;
int t;
This output is probably okay. The issue needs a bit
more discussion.
. gdb.mi/mi*-pthreads.exp: check mi_thread_command_set: -thread-select [3456]
PASS -> blank
blank -> PASS
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)
blank -> PASS
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.
PASS FAIL
thread 0 5 33
thread 1 35 3
thread 2 36 2
thread 3 37 1
thread 4 36 2
thread 5 38 0
. gdb 6.0
. suite HEAD
. gdb.base/break.exp: *
ERROR -> blank
FAIL -> blank
FAIL -> PASS
UNRESOLVED -> blank
UNRESOLVED -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.base/chng-syms.exp: running with invalidated bpt condition after executable changes
PASS -> blank
Fluctuation with unknown cause.
. 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.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.cp/rtti.exp: end of constructors in func3
blank -> PASS
gdb.cp/rtti.exp: print *obj3
blank -> FAIL
David C added some tests.
. gdb.cp/templates.exp: ptype quxint
PASS -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (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.
PASS FAIL
thread 0 1 11
thread 1 11 1
thread 2 11 1
thread 3 12 0
thread 4 12 0
thread 5 12 0
. gdb gdb_6_1-branch
. suite gdb_6-1-branch
. gdb.cp/rtti.exp: end of constructors in func3
blank -> PASS
gdb.cp/rtti.exp: print *obj3
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/templates.exp: ptype quxint
PASS -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (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.
PASS FAIL
thread 0 4 34
thread 1 34 4
thread 2 38 0
thread 3 38 0
thread 4 35 3
thread 5 38 0
. gdb gdb_6_1-branch
. suite HEAD
. 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.cp/templates.exp: ptype quxint
PASS -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.cp/rtti.exp: end of constructors in func3
blank -> PASS
gdb.cp/rtti.exp: print *obj3
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.0 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.
PASS FAIL
thread 0 3 9
thread 1 9 3
thread 2 10 2
thread 3 10 2
thread 4 11 1
thread 5 12 0
. gdb HEAD
. suite HEAD
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.cp/rtti.exp: end of constructors in func3
blank -> PASS
gdb.cp/rtti.exp: print *obj3
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/templates.exp: ptype quxint
PASS -> FAIL
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.
PASS FAIL
thread 0 2 36
thread 1 36 2
thread 2 38 0
thread 3 38 0
thread 4 36 2
thread 5 38 0
. gdb drow-cplus-branch
. suite drow-cplus-branch
. gdb.base/pending.exp: pending disabled
PASS -> FAIL
gdb.base/pending.exp: pending plus condition
PASS -> FAIL
FAIL -> PASS
Not analyzed.
. gdb.cp/templates.exp: ptype quxint
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.
PASS FAIL
thread 0 2 10
thread 1 12 0
thread 2 12 0
thread 3 11 1
thread 4 10 2
thread 5 12 0
. gdb drow-cplus-branch
. suite HEAD
. gdb.base/pending.exp: *
blank -> ERROR
blank -> FAIL
PASS -> FAIL
PASS -> UNRESOLVED
FAIL -> blank
FAIL -> PASS
FAIL -> UNRESOLVED
UNRESOLVED -> FAIL
Not analyzed.
. gdb.cp/rtti.exp: end of constructors in func3
blank -> PASS
gdb.cp/rtti.exp: print *obj3
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/templates.exp: ptype quxint
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.
PASS FAIL
thread 0 3 9
thread 1 11 1
thread 2 12 0
thread 3 11 1
thread 4 9 3
thread 5 12 0
. gdb drow_intercu-20040221-branch
. suite drow_intercu-20040221-branch
. gdb.cp/templates.exp: ptype quxint
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.
PASS FAIL
thread 0 3 9
thread 1 9 3
thread 2 9 3
thread 3 9 3
thread 4 10 2
thread 5 12 0
. gdb drow_intercu-20040221-branch
. suite HEAD
. gdb.base/pending.exp: *
blank -> ERROR
blank -> FAIL
PASS -> UNRESOLVED
PASS -> FAIL
FAIL -> blank
FAIL -> PASS
FAIL -> FAIL
FAIL -> UNRESOLVED
UNRESOLVED -> FAIL
Not analyzed.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.cp/rtti.exp: end of constructors in func3
blank -> PASS
gdb.cp/rtti.exp: print *obj3
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/templates.exp: ptype quxint
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.
PASS FAIL
thread 0 3 9
thread 1 11 1
thread 2 12 0
thread 3 11 1
thread 4 9 3
thread 5 12 0
. Package Versions
. This Spin
binutils HEAD 2004-03-06 18:14:04 UTC
binutils binutils-2_15-branch 2004-03-06 18:15:36 UTC
gcc tree-ssa-20020619-branch 2004-03-06 18:40:00 UTC
gcc HEAD 2004-03-06 18:48:11 UTC
gcc gcc-3_4-branch 2004-03-06 18:52:46 UTC
gcc gcc-3_3-branch 2004-03-06 18:57:25 UTC
gdb HEAD 2004-03-08 00:22:37 UTC
gdb drow-cplus-branch 2004-03-08 00:24:54 UTC
gdb drow_intercu-20040221-branch 2004-03-08 00:27:10 UTC
gdb gdb_6_1-branch 2003-03-08 00:29:13 UTC
. Last Spin
binutils HEAD 2004-02-29 14:07:33 UTC
binutils binutils-2_15-branch 2004-02-29 14:09:20 UTC
gcc tree-ssa-20020619-branch 2004-02-29 14:17:03 UTC
gcc HEAD 2004-02-29 14:24:31 UTC
gcc gcc-3_4-branch 2004-02-29 14:31:53 UTC
gcc gcc-3_3-branch 2004-02-29 14:38:57 UTC
gdb HEAD 2004-03-02 15:48:46 UTC
gdb drow-cplus-branch 2004-03-02 15:52:24 UTC
gdb drow_intercu-20040221-branch 2004-03-02 15:57:12 UTC
gdb gdb_6_1-branch 2004-03-02 16:13:14 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, gdb_6_1-branch, HEAD, drow-cplus-branch, drow_intercu-20040221-branch
suite => 6.0, gdb_6_1-branch, HEAD, drow-cplus-branch, drow_intercu-20040221-branch
cc => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.3, gcc gcc-3_3-branch, gcc gcc-3_4-branch, gcc HEAD, gcc tree-ssa-20020619-branch
as => binutils 2.13.90.0.2-rh, binutils 2.14, binutils binutils-2_15-branch, binutils HEAD
ld => binutils 2.13.90.0.2-rh, binutils 2.14, binutils binutils-2_15-branch, binutils HEAD
libc => glibc 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count => 186
'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 most configurations only with as binutils 2.14 and ld binutils
2.14. I test gdb 6.0 suite 6.0, gdb gdb_6_1-branch suite gdb_6-1-branch,
and gdb HEAD suite HEAD with the full spectrum of as and ld.
. 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
None.