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: Mon, 16 Feb 2004 22:15:36 -0500 (EST)
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
This is the last spin for gdb carlton_dictionary-branch. This branch
shows one remaining improvement in gdb/jmisc.exp which is not merged
into gdb HEAD.
The current tables are always at
http://www.shout.net/~mec/sunday/current/index.html
. Gdb Regression Summary
gdb HEAD versus gdb 6.0
gdb/826 gdb/931 gdb/1505 gdb/1512 gdb/1516
. Gcc Regression Summary
gcc 3.3.3-20040210 versus gcc 3.3.2
gcc gcc-3_3-branch versus gcc 3.3.2
No significant differences; no improvements or regressions.
gcc gcc-3_4-branch versus gcc 3.3.2
gcc/12267 gcc/13708 gcc/13956 gcc/13974
gdb/1537 gdb/1540
classes.exp unanalyzed regressions
gcc HEAD versus gcc 3.3.2
gcc/12267 gcc/13708 gcc/13956 gcc/13974
gdb/1537 gdb/1540
classes.exp unanalyzed regressions
gcc tree-ssa-20020619-branch versus gcc HEAD
gcc/14048 gcc/14049
. Old Bugs Fixed
None.
. New Bugs Detected
None.
. PR Count
Query executed 2004-02-16 22:27:30 UTC
1555 matches found
22 analyzed
723 closed
25 feedback
766 open
3 paperwork
16 suspended
1555 TOTAL
. Libiberty Testing
. target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
binutils HEAD 742 tests, 0 failures
gcc gcc-3_3-branch 649 tests, 0 failures
gcc gcc-3_4-branch 742 tests, 0 failures
gcc HEAD 742 tests, 0 failures
gcc tree-ssa-20020619-branch 742 tests, 0 failures
gdb HEAD 742 tests, 0 failures
gdb carlton_dictionary-branch 742 tests, 0 failures
gdb drow-cplus-branch 742 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-02-15/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-02-11/index.html
. Non-Pass Results
gdb 6.0
suite 6.0 457 non-PASS results
suite HEAD 621 non-PASS results
gdb HEAD
suite HEAD 452 non-PASS results
gdb carlton_dictionary-branch
suite carlton_dictionary-branch 481 non-PASS results
suite HEAD 460 non-PASS results
gdb drow-cplus-branch
suite drow-cplus-branch 614 non-PASS results
suite HEAD 586 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: *
gdb.cp/pr-1210.exp: *
gdb.cp/userdef.exp: *
gdb.java/jmisc1.exp: *
gdb.java/jmisc2.exp: *
gdb.objc/basicclass.exp: *
blank -> ERROR
PASS -> FAIL
PASS -> UNRESOLVED
FAIL -> blank
This happened with gcc tree-ssa-20020619-branch -gdwarf-2
and gcc tree-ssa-20020619-branch -gstabs+.
gcc tree-ssa-20020619-branch merged the code from gdb HEAD to
generate dwarf-2 location lists. gdb 6.0 crashes when it
encounters a dwarf-2 location list.
Even when I compile the test program with gcc -gstabs+, the
run-time libraries for C++, Java, and Objective-C have their
own debugging symbols. These symobls are in dwarf-2 format.
. 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 gcc-3_4-branch and gcc HEAD,
with dwarf-2 and stabs+. 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]
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
blank -> PASS
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
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 29
thread 1 27 3
thread 2 29 1
thread 3 30 0
thread 4 30 0
thread 5 30 0
. gdb 6.0
. suite HEAD
. gdb.base/break.exp: *
gdb.cp/bs15503.exp: *
gdb.cp/pr-1210.exp: *
gdb.cp/userdef.exp: *
gdb.java/jmisc1.exp: *
gdb.java/jmisc2.exp: *
gdb.objc/basicclass.exp: *
blank -> ERROR
blank -> FAIL
blank -> UNRESOLVED
PASS -> blank
PASS -> UNRESOLVED
PASS -> FAIL
FAIL -> blank
Same analysis as gdb 6.0 suite 6.0.
. 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.cp/breakpoint.exp: setting breakpoint at C1::Nested::foo
blank -> FAIL
gdb.cp/breakpoint.exp: continue to C1::Nested:foo
blank -> FAIL
David C wrote a new test script.
. gdb.cp/templates.exp: ptype quxint
PASS -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.mi/mi1-*.exp: *
PASS -> blank
FAIL -> blank
KFAIL -> blank
XFAIL -> blank
Andrew C deleted the mi level 1 tests.
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
blank -> PASS
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 1 29
thread 1 27 3
thread 2 29 1
thread 3 30 0
thread 4 30 0
thread 5 30 0
. gdb HEAD
. 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.cp/breakpoint.exp: continue to C1::Nested::foo
blank -> PASS
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. With gdb HEAD, this
happened with gcc gcc-3_4-branch -gstabs+ and gcc HEAD
-gstabs+.
. gdb.java/jmisc.exp: program timed out
blank -> WARNING
gdb.java/jmisc.exp: *
* -> *
One configuration of gdb timed out while running gcj. This
was probably a false timeout caused by other activity on my
test bed machine while gcj was running.
. gdb.mi/mi1-*.exp: *
PASS -> blank
FAIL -> blank
KFAIL -> blank
XFAIL -> blank
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 4 26
thread 1 27 3
thread 2 30 0
thread 3 30 0
thread 4 29 1
thread 5 30 0
. gdb carlton_dictionary-branch
gdb carlton_dictionary-branch has been retired. This is the last
spin for this branch.
There were no significant changes since the previous spin.
I compared gdb HEAD versus gdb carlton_dictionary_branch using the
gdb HEAD test suite. One test script showed improvement:
gdb.java/jmisc.exp with gcc 3.3.2, gcc 3.3.3-20040210, and gcc
gcc-3_3-branch, both dwarf-2 and stabs+.
# gdb HEAD
(gdb) break jmisc.main
the class jmisc does not have any method named main
Hint: try 'jmisc.main<TAB> or 'jmisc.main<ESC-?>
(Note leading single quote.)
(gdb) FAIL: gdb.java/jmisc.exp: setting breakpoint at jmisc.main
# gdb carlton_dictionary-branch
(gdb) break jmisc.main
Breakpoint 1 at 0x804ae1e: file /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.java/jmisc.java, line 6.
. gdb drow-cplus-branch
. suite drow-cplus-branch
. gdb.base/pending.exp: pending plus condition
FAIL -> PASS
PASS -> FAIL
Not analyzed.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> 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. With gdb
drow-cplus-branch, this happened with gcc gcc-3_4-branch
-gstabs+ and gcc HEAD -gstabs+.
. 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 10
thread 1 12 2
thread 2 12 2
thread 3 11 3
thread 4 12 2
thread 5 14 0
. gdb drow-cplus-branch
. suite HEAD
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.cp/breakpoint.exp: setting breakpoint at C1::Nested::foo
blank -> FAIL
gdb.cp/breakpoint.exp: continue to C1::Nested:foo
blank -> FAIL
blank -> UNRESOLVED
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/bs15503.exp: running to main in runto (timeout)
UNRESOLVED -> FAIL
This happened with gcc 2.95.3 -gstabs+. This is a cascade
problem from the previous test script.
. gdb.cp/templates.exp: ptype quxint
PASS -> FAIL
Same analysis as gdb 6.0 suite 6.0. With gdb
drow-cplus-branch, this happened with gcc gcc-3_4-branch
-gstabs+ and gcc HEAD -gstabs+.
. gdb.mi/mi1-*.exp: *
PASS -> blank
FAIL -> blank
KFAIL -> blank
XFAIL -> blank
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 4 10
thread 1 11 3
thread 2 14 0
thread 3 13 1
thread 4 12 2
thread 5 14 0
. 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, HEAD, carlton_dictionary-branch, drow-cplus-branch
suite => 6.0, carlton_dictionary-branch, drow-cplus-branch, HEAD
cc => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.2, gcc 3.3.3-20040210, 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 HEAD
ld => binutils 2.13.90.0.2-rh, binutils 2.14, binutils HEAD
libc => glibc 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count => 146
'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 carlton_dictionary_branch and gdb drow-cplus-branch only
with as/ld from binutils 2.14, not with vendor as/ld or binutils HEAD
as/ld. This means I do not test c_d-b and d-c-b with vendor gcc.
I test each version gdb with its own gdb-test-suite and also with
gdb-test-suite HEAD.
. Package Versions
. This Spin
binutils HEAD 2004-02-14 10:07:33 UTC
gcc tree-ssa-20020619-branch 2004-02-14 10:18:26 UTC
gcc HEAD 2004-02-14 10:30:59 UTC
gcc gcc-3_4-branch 2004-02-14 10:36:50 UTC
gcc gcc-3_3-branch 2004-02-14 10:46:11 UTC
gdb HEAD 2004-02-15 06:12:22 UTC
gdb carlton_dictionary-branch 2004-02-15 06:15:06 UTC
gdb drow-cplus-branch 2004-02-15 06:16:58 UTC
. Last Spin
binutils HEAD 2004-02-10 17:39:23 UTC
gcc tree-ssa-20020619-branch 2004-02-10 17:46:07 UTC
gcc HEAD 2004-02-10 18:02:01 UTC
gcc gcc-3_4-branch 2004-02-10 18:14:15 UTC
gcc gcc-3_3-branch 2004-02-10 18:24:30 UTC
gdb HEAD 2004-02-11 15:06:00 UTC
gdb carlton_dictionary-branch 2004-02-11 15:08:16 UTC
gdb drow-cplus-branch 2004-02-11 15:10:24 UTC
. 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 dropped gcc 3.3.3-20040131.
This is the last spin for gdb carlton_dictionary-branch.