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
- Cc: drow at mvista dot com
- Date: Fri, 27 Feb 2004 16:54:55 -0500 (EST)
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
I added gdb drow_intercu-20040221-branch. There is one regression
in gdb.cp/namespace.exp, one significant improvement, and one
improvement which looks accidental.
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/1563
. 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
None.
. New Bugs Detected Since Last Spin
None.
. PR Count
Query executed 2004-02-27 18:05:23 UTC
1576 matches found
21 analyzed
736 closed
25 feedback
775 open
3 paperwork
16 suspended
1576 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 742 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
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-26/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-02-21/index.html
. Non-Pass Results
gdb 6.0
suite 6.0 457 non-PASS results
suite HEAD 618 non-PASS results
gdb HEAD
suite HEAD 469 non-PASS results
gdb drow-cplus-branch
suite drow-cplus-branch 613 non-PASS results
suite HEAD 613 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 437 non-PASS results
suite HEAD 461 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)
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 2 36
thread 1 38 0
thread 2 37 1
thread 3 38 0
thread 4 37 1
thread 5 38 0
. gdb 6.0
. suite HEAD
. gdb.base/freebpcmd.exp: run program with breakpoint commands
PASS -> KFAIL
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
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.java/jmisc.exp: setting breakpoint at jmisc.main
FAIL -> blank
gdb.java/jmisc.exp: running to 'jmisc.main(java.lang.String[])' in runto
blank -> FAIL
gdb.java/jmisc.exp: p *args
gdb.java/jmisc.exp: p args
FAIL -> blank
FAIL -> PASS
gdb.java/jmisc.exp: ptype jmisc
FAIL -> FAIL
Andrew C changed jmisc.exp to be the same as jmisc2.exp. This
is actually a regression in the test script, not an
improvement in gdb or gcc.
. 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 2 10
thread 1 10 2
thread 2 12 0
thread 3 12 0
thread 4 12 0
thread 5 12 0
. gdb HEAD
. suite HEAD
. gdb.base/langs.exp: *
PASS -> blank
blank -> ERROR
blank -> FAIL
blank -> UNRESOLVED
gdb changed. The test script needs to be updated.
# gdb.log
(gdb) b langs0
Function "langs0" not defined.
Make breakpoint pending on future shared library load? (y or [n]) FAIL: gdb.base/langs.exp: break on nonexistent function in langs.exp (timeout)
This has been fixed already in gdb HEAD.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/templates.exp: ptype Baz
KFAIL -> FAIL
This happened with gcc 3.2-7-rh, gcc 3.3.3, and gcc
gcc-3_3-branch with dwarf-2.
# gdb.log 2004-02-21
ptype Baz
type = class Baz<int, 115> {
# gdb.log 2004-02-26
ptype Baz
type = class Baz<int, (char)115> {
I consider this output from gdb to be okay.
. gdb.java/jmisc.exp: setting breakpoint at jmisc.main
FAIL -> blank
gdb.java/jmisc.exp: running to 'jmisc.main(java.lang.String[])' in runto
blank -> FAIL
gdb.java/jmisc.exp: p *args
gdb.java/jmisc.exp: p args
FAIL -> PASS
Same analysis as gdb 6.0 suite HEAD.
. 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 4 34
thread 1 37 1
thread 2 37 1
thread 3 37 1
thread 4 37 1
thread 5 38 0
. gdb drow-cplus-branch
. suite drow-cplus-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 10 2
thread 2 11 1
thread 3 12 0
thread 4 11 1
thread 5 12 0
. gdb drow-cplus-branch
. suite HEAD
. gdb.base/pending.exp: *
blank -> ERROR
PASS -> FAIL
PASS -> UNRESOLVED
This is a skew problem between gdb drow-cplus-branch and suite
HEAD. The pending-breakpoint code in suite HEAD works with
gdb 6.0 and gdb HEAD, but not with gdb drow-cplus-branch.
# gdb.log
(gdb) break pendfunc1
Function "pendfunc1" not defined.
Make breakpoint pending on future shared library load? (y or n) ERROR: Got interactive prompt.
UNRESOLVED: gdb.base/pending.exp: set pending breakpoint
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.java/jmisc.exp: setting breakpoint at jmisc.main
FAIL -> blank
gdb.java/jmisc.exp: running to 'jmisc.main(java.lang.String[])' in runto
blank -> FAIL
gdb.java/jmisc.exp: p *args
gdb.java/jmisc.exp: p args
FAIL -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb drow_intercu-20040221-branch
. suite drow_intercu-20040221-branch
This is the first spin for gdb drow_intercu-20040221-branch.
I ran this gdb branch with its own test suite but did not analyze
the results.
. suite HEAD
This is the first spin for gdb drow_intercu-20040221-branch.
I ran this gdb branch with gdb test suite HEAD and compared it to
gdb HEAD suite HEAD.
. gdb.base/langs.exp: *
* -> *
This is an issue with pending breakpoints. test suite HEAD
works with the older code in gdb drow_intercu-20040221-branch,
but not with the newer code in gdb HEAD.
. gdb.base/pending.exp
* -> *
This is an issue with pending breakpoints. test suite HEAD
works with the newer code in gdb HEAD, but not with the older
code in gdb drow_intercu-20040221-branch.
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/namespace.exp: ptype CClass::NestedClass
PASS -> FAIL
This happened with gcc gcc-3_4-branch, gcc HEAD, and gcc
tree-ssa-20020619-branch with dwarf-2. This looks like a
regression in gdb drow_intercu-20040221-branch.
# gdb.log gdb HEAD
ptype CClass::NestedClass
type = class C::CClass::NestedClass {
public:
int y;
}
(gdb) PASS: gdb.cp/namespace.exp: ptype CClass::NestedClass
# gdb.log gdb drow_intercu-20040221-branch
(gdb) FAIL: gdb.cp/namespace.exp: ptype CClass::NestedClass
ptype NestedClass
No symbol "NestedClass" in current context.
. gdb.cp/templates.exp: ptype Baz
FAIL -> KFAIL
This happened with gcc 3.2-7-rh, gcc 3.3.3, and gcc
gcc-3_3-branch with dwarf-2.
# gdb.log gdb HEAD
ptype Baz
type = class Baz<int, (char)115> {
# gdb.log gdb drow_intercu-20040221-branch
ptype Baz
type = class Baz<int, 115> {
This looks like more like a very recent bug in gdb HEAD rather
than a bug fix in gdb drow_intercu-20040221-branch.
. gdb.mi/mi-var-display.exp: assing to variable bar
gdb.mi/mi-var-display.exp: create local variable bar
gdb.mi/mi-var-display.exp: eval variable bar
gdb.mi/mi-var-display.exp: eval variable bar with new format
gdb.mi/mi-var-display.exp: eval variable bar with new value
gdb.mi/mi-var-display.exp: info type variable bar
gdb.mi/mi2-var-display.exp: assing to variable bar
gdb.mi/mi2-var-display.exp: create local variable bar
gdb.mi/mi2-var-display.exp: eval variable bar
gdb.mi/mi2-var-display.exp: eval variable bar with new format
gdb.mi/mi2-var-display.exp: eval variable bar with new value
gdb.mi/mi2-var-display.exp: info type variable bar
FAIL -> PASS
gdb drow_intercu-20040221-branch is better than gdb HEAD.
This happened with gcc 2.95.3 -gdwarf-2.
. 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 8 4
thread 2 12 1
thread 3 12 0
thread 4 12 1
thread 5 12 0
. Package Versions
. This 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
. Last Spin
binutils HEAD 2004-02-20 04:30:06 UTC
binutils binutils-2_15-branch 2004-02-20 04:31:40 UTC
gcc tree-ssa-20020619-branch 2004-02-20 04:36:00 UTC
gcc HEAD 2004-02-20 04:42:39 UTC
gcc gcc-3_4-branch 2004-02-20 04:48:22 UTC
gcc gcc-3_3-branch 2004-02-20 04:54:22 UTC
gdb HEAD 2004-02-21 10:34:37 UTC
gdb drow-cplus-branch 2004-02-21 10:38:45 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, HEAD, drow-cplus-branch, drow_intercu-20040221-branch
suite => 6.0, drow-cplus-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 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 => 136
'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 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 drow_intercu-20040221-branch.
gcc 3.3.3 has been officially released. The official tarball is
identical to the unofficial tarball that I used last spin.
I dropped gcc 3.3.2 and gcc 3.3.3-20040210.