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: Fri, 5 Mar 2004 12:49:20 -0500 (EST)
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
I added gdb gdb_6_1-branch. Compared with gdb HEAD, there are no
regressions and no improvements.
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; 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
. gdb HEAD
http://sources.redhat.com/gdb/bugs/1563
Regression printing large integers
Jeff J fixed this bug.
. New Bugs Detected Since Last Spin
None.
. PR Count
Query executed 2004-03-05 15:44:13 UTC
1581 matches found
22 analyzed
739 closed
25 feedback
776 open
3 paperwork
16 suspended
1581 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 742 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-02/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-02-26/index.html
. Non-Pass Results
gdb 6.0
suite 6.0 459 non-PASS results
suite HEAD 620 non-PASS results
gdb gdb_6_1-banch
suite gdb_6_1-branch 465 non-PASS results
suite HEAD 449 non-PASS results
gdb HEAD
suite HEAD 464 non-PASS results
gdb drow-cplus-branch
suite drow-cplus-branch 611 non-PASS results
suite HEAD 621 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 438 non-PASS results
suite HEAD 465 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.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)
blank -> PASS
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.
PASS FAIL
thread 0 4 34
thread 1 37 1
thread 2 37 1
thread 3 37 1
thread 4 37 1
thread 5 38 0
. gdb 6.0
. suite HEAD
. gdb.base/charset.exp: check value of "\e" in *
gdb.base/charset.exp: check value of '\e' in *
gdb.base/charset.exp: try printing '\e' in *
PASS -> blank
Andrew C improved the test script.
. gdb.base/chng-syms.exp: running with invalidated bpt condition after executable changes
blank -> PASS
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.base/printcmds.exp: p ctable1[27]
gdb.base/printcmds.exp: p &ctable1[3*8]
PASS -> FAIL
Andrew C improved the test script. The new script no longer
accepts the output of gdb 6.0, which did not change.
. gdb.base/setvar.exp: set variable char=27 (Esc)
gdb.base/setvar.exp: set variable signed char=27 (Esc)
gdb.base/setvar.exp: set variable unsigned char=27 (Esc)
PASS -> blank
gdb.base/setvar.exp: set variable char=7 (Bel)
gdb.base/setvar.exp: set variable signed char=7 (Bel)
gdb.base/setvar.exp: set variable unsigned char=7 (Bel)
blank -> PASS
Andrew C improved the test script.
. 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.cp/class2.exp: print object with no data fields
blank -> PASS
Joel B improved the test script.
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (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 1 11
thread 1 11 1
thread 2 12 0
thread 3 12 0
thread 4 12 0
thread 5 12 0
. gdb gdb_6_1-branch
. suite gdb_6_1-branch
This is the first spin with gdb gdb_6_1-branch. I compared these
results with gdb gdb_6_1-branch suite HEAD. There were no
significant improvements or regregressions.
. suite HEAD
This is the first spin with gdb gdb_6_1-branch. I compared these
results with gdb HEAD suite HEAD. There were no significant
improvements or regressions.
. gdb HEAD
. suite HEAD
. gdb.base/charset.exp: check value of "\e" in *
gdb.base/charset.exp: check value of '\e' in *
gdb.base/charset.exp: try printing '\e' in *
PASS -> blank
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/langs.exp: *
ERROR -> blank
FAIL -> blank
UNRESOLVED -> blank
blank -> PASS
Jeff J improved the test script.
. gdb.base/setvar.exp: set variable char=27 (Esc)
gdb.base/setvar.exp: set variable signed char=27 (Esc)
gdb.base/setvar.exp: set variable unsigned char=27 (Esc)
PASS -> blank
gdb.base/setvar.exp: set variable char=7 (Bel)
gdb.base/setvar.exp: set variable signed char=7 (Bel)
gdb.base/setvar.exp: set variable unsigned char=7 (Bel)
blank -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/annota3.exp: annotate-quit
KFAIL -> PASS
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/class2.exp: print object with no data fields
blank -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb.stabs/weird.exp: print very big integer
FAIL -> PASS
Jeff J fixed a bug in gdb.
http://sources.redhat.com/gdb/bugs/1563
Regression printing large integers
. 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 4 34
thread 1 37 1
thread 2 38 0
thread 3 36 2
thread 4 36 2
thread 5 38 0
. gdb drow-cplus-branch
. suite drow-cplus-branch
. gdb.base/pending.exp: pending plus condition
PASS -> FAIL
FAIL -> PASS
Not analyzed.
. 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 9 3
thread 2 12 0
thread 3 12 0
thread 4 12 0
thread 5 12 0
. gdb drow-cplus-branch
. suite HEAD
. gdb.base/charset.exp: check value of "\e" in *
gdb.base/charset.exp: check value of '\e' in *
gdb.base/charset.exp: try printing '\e' in *
PASS -> blank
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/langs.exp: *
blank -> ERROR
blank -> UNRESOLVED
PASS -> blank
PASS -> UNRESOLVED
Not analyzed. This is likely to be a skew problem with the
"pending breakpoint" prompt.
. gdb.base/pending.exp: breakpoint function
gdb.base/pending.exp: rerun to main
PASS -> FAIL
FAIL -> PASS
gdb.base/pending.exp: find line number containing "break main here"
blank -> FAIL
FAIL -> blank
Not analyzed.
. gdb.base/printcmds.exp: p ctable1[27]
gdb.base/printcmds.exp: p &ctable1[3*8]
PASS -> FAIL
Not analyzed, but likely to be the same analysis as
gdb 6.0 suite HEAD.
. gdb.base/setvar.exp: set variable char=27 (Esc)
gdb.base/setvar.exp: set variable signed char=27 (Esc)
gdb.base/setvar.exp: set variable unsigned char=27 (Esc)
PASS -> blank
gdb.base/setvar.exp: set variable char=7 (Bel)
gdb.base/setvar.exp: set variable signed char=7 (Bel)
gdb.base/setvar.exp: set variable unsigned char=7 (Bel)
blank -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/class2.exp: print object with no data fields
blank -> PASS
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 11 1
thread 2 12 0
thread 3 11 1
thread 4 11 1
thread 5 12 0
. gdb drow_intercu-20040221-branch
. suite drow_intercu-20040221-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.
PASS FAIL
thread 0 3 9
thread 1 7 5
thread 2 11 1
thread 3 12 0
thread 4 12 0
thread 5 12 0
. gdb drow_intercu-20040221-branch
. suite HEAD
. gdb.base/charset.exp: check value of "\e" in *
gdb.base/charset.exp: check value of '\e' in *
gdb.base/charset.exp: try printing '\e' in *
PASS -> blank
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/langs.exp: *
blank -> ERROR
blank -> UNRESOLVED
PASS -> blank
PASS -> UNRESOLVED
Not analyzed. This is likely to be a skew problem with the
"pending breakpoint" prompt.
. gdb.base/pending.exp: *
blank -> FAIL
ERROR -> blank
PASS -> FAIL
FAIL -> blank
FAIL -> PASS
FAIL -> UNRESOLVED
UNRESOLVED -> PASS
UNRESOLVED -> FAIL
Not analyzed.
. gdb.base/printcmds.exp: p ctable1[27]
gdb.base/printcmds.exp: p &ctable1[3*8]
PASS -> FAIL
Not analyzed, but likely to be the same analysis as
gdb 6.0 suite HEAD.
. gdb.base/setvar.exp: set variable char=27 (Esc)
gdb.base/setvar.exp: set variable signed char=27 (Esc)
gdb.base/setvar.exp: set variable unsigned char=27 (Esc)
PASS -> blank
gdb.base/setvar.exp: set variable char=7 (Bel)
gdb.base/setvar.exp: set variable signed char=7 (Bel)
gdb.base/setvar.exp: set variable unsigned char=7 (Bel)
blank -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/class2.exp: print object with no data fields
blank -> PASS
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 1 11
thread 1 11 1
thread 2 12 0
thread 3 12 0
thread 4 12 0
thread 5 12 0
. Package Versions
. This 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
. Last Spin
binutils HEAD 2004-02-24 22:20:50 UTC
binutils binutils-2_15-branch 2004-02-24 22:22:26 UTC
gcc tree-ssa-20020619-branch 2004-02-24 22:49:14 UTC
gcc HEAD 2004-02-24 22:56:13 UTC
gcc gcc-3_4-branch 2004-02-24 23:01:41 UTC
gcc gcc-3_3-branch 2004-02-24 23:07:14 UTC
gdb HEAD 2004-02-26 02:39:40 UTC
gdb drow-cplus-branch 2004-02-26 02:41:41 UTC
gdb drow_intercu-20040221-branch 2004-02-26 02:44:05 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
I added gdb gdb_6_1-branch and suite gdb_6_1-branch.