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: Wed, 14 Jul 2004 04:02:40 -0400 (EDT)
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
It's been 19 days since the last spin, which is longer than usual.
During this time there were three new debug info regressions in gcc
and one in binutils. All of them have been fixed. This is on top
of some old bugs that were fixed too. So my test bed was doing
something useful, spotting bugs, but I wasn't able to make a useful
report for a while.
I added gcc 3.3.4. It's healthy.
I gcc 3.4.1-20040625 and gcc 3.4.1. They are both healthy.
I haven't added gdb gdb-6_2-branch yet. Next spin.
This will be the last spin for gdb gdb-6_1-branch.
This will be the last spin for binutils-2_15-branch if there is no
more activity on the branch. The last activity on this branch
was 2004-05-23.
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
not analyzed
gdb HEAD versus gdb 6.1.1
gdb/1650
gdb gdb_6_1-branch versus gdb 6.1.1
no improvements and no regressions
. Gcc Regression Summary
gcc HEAD versus gcc 3.4.0
gcc/13974 gcc/14049 gcc/14860
gdb/1656
gcc gcc-3_4-branch versus gcc 3.4.0
gcc 3.4.1 versus gcc 3.4.0
gcc 3.4.1-20040625 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
gcc 3.3.4 versus gcc 3.3.3
gcc 3.3.4-20040530 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.15
binutils binutils_2-15-branch versus binutils 2.15
no improvements and no regressions
. Old Bugs Fixed Since Last Spin
. gdb HEAD
http://sources.redhat.com/gdb/bugs/1056
divide by zero hangs gdb
David Lecomber partially fixed this bug. Most of the cases
that users will encounter are completely fixed.
http://sources.redhat.com/gdb/bugs/1677
[regression] selftest.exp, crash in lookup_symtab
Bob Rossi fixed this.
pr gdb/1704 is likely to be the same bug.
. gcc HEAD
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14049
[3.5 regression] bad debug block info, dwarf-2, c++
This PR describes two separate bugs (my bad).
Someone fixed one of the bugs; the other bug still happens.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15721
[3.5 regression] template instantation omits static data members
Andrew Pinski fixed this.
. New Bugs Detected Since Last Spin
None.
. PR Count
Query executed 2004-07-14 02:49:55 UTC
1708 matches found
23 analyzed
780 closed
22 feedback
863 open
3 paperwork
17 suspended
1708 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 746 tests, 0 failures
gcc gcc-3_3-branch 649 tests, 0 failures
gcc gcc-3_4-branch 745 tests, 0 failures
gcc HEAD 746 tests, 0 failures
gdb HEAD 746 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.15.
The binutils version should not make a difference.
. Gdb Testing
My tables are at
http://www.shout.net/~mec/sunday/2004-07-08/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-06-19/index.html
. Non-Pass Results
gdb 6.1.1
suite 6.1.1 994 non-PASS results
suite HEAD 972 non-PASS results
gdb gdb_6_1-banch
suite gdb_6_1-branch 996 non-PASS results
suite HEAD 971 non-PASS results
gdb HEAD
suite HEAD 969 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 1004 non-PASS results
suite HEAD 975 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.1.1
. suite 6.1.1
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
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.cp/local.exp: ptype Local
gdb.cp/local.exp: ptype l
FAIL -> PASS
This happened with gcc HEAD -gdwarf-2.
Someone fixed a bug in gcc.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14049
[3.5 regression] bad debug block info, dwarf-2, c++
PR gcc/14049 actually describes two separate bugs,
and only one of them was fixed. The PR is still open.
. gdb.cp/m-static.exp: derived template object, static enum
gdb.cp/m-static.exp: template object, static derived enum
FAIL -> PASS
This happened with gcc HEAD -gstabs+.
Andrew Pinski fixed a bug in gcc.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15721
[3.5 regression] template instantation omits static data members
. gdb.cp/templates.exp: ptype quxint
PASS -> FAIL
This happened with gcc HEAD -gstabs+.
This is a problem in the test script. The compiler changed
the whitespace in the symbol name with -gstabs+.
# gcc HEAD 2004-06-17
ptype quxint
type = class Qux<int,(char*)(&string)> {
# gcc HEAD 2004-07-06
ptype quxint
type = class Qux<int,(char*)(& string)> {
Michael Chastain improved the script in suite HEAD to accept
both forms.
. 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.
t0 t1 t2 t3 t4 t5
PASS 9 62 59 62 57 62
FAIL 53 0 3 0 5 0
. gdb 6.1.1
. suite HEAD
. gdb.arch/i386-sse.exp: *
blank -> UNSUPPORTED
ERROR -> blank
WARNING -> blank
FAIL -> blank
UNRESOLVED -> blank
Jim Blandy and Michael Chastain improved the test script.
All results are now PASS or UNSUPPORTED. The UNSUPPORTED
results happened with gcc 2.95.3, which is fine.
. gdb.base/sigbpt.exp:*
blank -> PASS
blank -> KFAIL
Andrew Cagney wrote a new test script.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.1.1 suite 6.1.1.
. gdb.cp/pr-1553.exp: ptype E::F
gdb.cp/pr-1553.exp: ptype c_var
PASS -> blank
FAIL -> blank
Michael Chastain removed this test script.
. gdb.java/jmain.exp: *
blank -> PASS
blank -> KFAIL
blank -> UNTESTED
. gdb.java/jmisc2.exp: *
PASS -> blank
FAIL -> blank
UNTESTED -> blank
Andrew Cagney reorganized the java scripts.
. gdb.java/jmisc.exp: ptype jmisc
gdb.java/jmisc1.exp: ptype jmisc
FAIL -> PASS
FAIL -> PASS
Jeff Johnston improved the test scripts.
. gdb.mi/mi-file.exp: Undefined command "222-file-list-exec-source-files".
blank -> ERROR
gdb.mi/mi-file.exp: Getting a list of source files.
blank -> UNRESOLVED
gdb.mi/mi2-file.exp: Undefined command "222-file-list-exec-source-files".
ERROR -> blank
gdb.mi/mi2-file.exp: Getting a list of source files.
UNRESOLVED -> blank
Bob Rossi moved some tests from mi2-file.exp to mi-file.exp.
. 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 19 18 20 20 20
FAIL 17 1 2 0 0 0
. gdb gdb_6_1-branch
. suite gdb_6_1-branch
suite HEAD
As of this writing, gdb gdb_6_2-branch has been created,
so gdb gdb_6_1-branch is dead.
I included it in this spin -- the new branch was created after I
started the spin. I examined the tables and found nothing
noteworthy.
. gdb HEAD
. suite HEAD
. gdb.arch/i386-sse.exp: *
gdb.base/sigbpt.exp: *
gdb.cp/pr-1553.exp: ptype E::F
gdb.cp/pr-1553.exp: ptype c_var
gdb.java/jmain.exp: *
gdb.java/jmisc2.exp: *
gdb.java/jmisc.exp: ptype jmisc
gdb.java/jmisc1.exp: ptype jmisc
gdb.mi/mi-file.exp: *
gdb.mi/mi2-file.exp: *
* -> *
Same analyses as gdb 6.1 suite HEAD.
. gdb.base/gdb1056.exp: print 1/0
KFAIL -> PASS
David Lecomber partially fixed a bug in gdb.
http://sources.redhat.com/gdb/bugs/1056
divide by zero hangs gdb
. gdb.base/selftest.exp: *
blank -> PASS
FAIL -> PASS
Bob Rossi fixed a bug in gdb.
http://sources.redhat.com/gdb/bugs/1677
[regression] selftest.exp, crash in lookup_symtab
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
KFAIL -> PASS
. gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.1.1 suite 6.1.1.
. gdb.cp/local.exp: ptype Local
gdb.cp/local.exp: ptype l
FAIL -> PASS
Same analysis as gdb 6.1.1 suite 6.1.1
. gdb.cp/m-static.exp: derived template object, static enum
gdb.cp/m-static.exp: template object, static derived enum
FAIL -> PASS
Same analysis as gdb 6.1.1 suite 6.1.1.
. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
FAIL -> FAIL
This is a bug in gdb. It happens intermittently.
http://sources.redhat.com/gdb/bugs/1650
manythreads.exp
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
blank -> PASS
Same analysis as gdb 6.1.1 suite 6.1.1.
. 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 61 61 62 57 62
FAIL 54 1 1 0 5 0
. gdb drow_intercu-20040221-branch
. suite drow_intercu-20040221-branch
The last change on this branch was 2004-04-19.
I examined the tables and nothing noteworthy.
. suite HEAD
. gdb.arch/i386-sse.exp: *
gdb.base/sigbpt.exp: *
gdb.cp/pr-1553.exp: ptype E::F
gdb.cp/pr-1553.exp: ptype c_var
gdb.java/jmain.exp: *
gdb.java/jmisc2.exp: *
gdb.java/jmisc.exp: ptype jmisc
gdb.java/jmisc1.exp: ptype jmisc
gdb.mi/mi-file.exp: *
gdb.mi/mi2-file.exp: *
* -> *
Same analyses as gdb 6.1 suite HEAD.
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.1.1 suite 6.1.1.
. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb HEAD suite HEAD.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
PASS -> blank
Same analysis as gdb 6.1.1 suite 6.1.1.
. gdb.threads/pthread_cond_wait.exp: backtrace in blocked thread
PASS -> FAIL
This happened with gcc HEAD -gstabs+.
gdb.log excerpt:
thread apply all backtrace
Thread 3 (Thread 8194 (LWP 12434)):
#0 0x420da1be in clone () from /lib/i686/libc.so.6
#1 0x40024990 in pthread_start_thread () from /lib/i686/libpthread.so.0
#2 0x40870be0 in ?? ()
#3 0x00000000 in ?? ()
#4 0x40870be0 in ?? ()
#5 0x00000000 in ?? ()
#6 0x00000000 in ?? ()
#7 0x00000000 in ?? ()
#8 0x00000000 in ?? ()
#9 0x00000000 in ?? ()
#10 0x00000000 in ?? ()
#11 0x00000000 in ?? ()
#12 0x00000000 in ?? ()
#13 0x00000000 in ?? ()
#14 0x00000000 in ?? ()
#15 0x00000000 in ?? ()
#16 0x00000000 in ?? ()
#17 0x00000000 in ?? ()
#18 0x4002b080 in __pthread_sig_debug () from /lib/i686/libpthread.so.0
#19 0x4002b080 in __pthread_sig_debug () from /lib/i686/libpthread.so.0
#20 0x00000000 in ?? ()
#21 0x00000000 in ?? ()
#22 0x00002002 in ?? ()
#23 0x00003092 in ?? ()
#24 0x00000000 in ?? ()
#25 0x4002de40 in __pthread_handles () from /lib/i686/libpthread.so.0
#26 0x00000000 in ?? ()
#27 0x00000000 in ?? ()
#28 0x00000000 in ?? ()
#29 0x00000000 in ?? ()
#30 0x00000000 in ?? ()
#31 0x00000000 in ?? ()
#32 0x00000000 in ?? ()
#33 0x00000000 in ?? ()
#34 0x00000000 in ?? ()
#35 0x00000000 in ?? ()
#36 0x00000000 in ?? ()
#37 0x080485b4 in noreturn () at /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.threads/pthread_cond_wait.c:47
Previous frame inner to this frame (corrupt stack?)
59 }
(gdb) FAIL: gdb.threads/pthread_cond_wait.exp: backtrace in blocked thread
I won't file a PR against gdb drow_intercu-20040221-branch for
this. If this happens with gdb HEAD it will be interesting.
. 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 20 20 20 19 20
FAIL 19 0 0 0 1 0
. Package Versions
. This Spin
binutils HEAD 2004-07-06 11:33:16 UTC
binutils binutils-2_15-branch 2004-07-06 11:38:28 UTC
gcc HEAD 2004-07-06 12:02:23 UTC
gcc gcc-3_4-branch 2004-07-06 12:16:16 UTC
gcc gcc-3_3-branch 2004-07-06 12:32:44 UTC
gdb HEAD 2004-07-08 17:15:37 UTC
gdb drow_intercu-20040221-branch 2004-07-08 17:29:17 UTC
gdb gdb_6_1-branch 2004-07-08 17:36:08 UTC
. Last Spin
binutils HEAD 2004-06-17 18:55:08 UTC
binutils binutils-2_15-branch 2004-06-17 18:58:51 UTC
gcc HEAD 2004-06-17 19:02:54 UTC
gcc gcc-3_4-branch 2004-06-17 19:11:35 UTC
gcc gcc-3_3-branch 2004-06-17 19:20:18 UTC
gdb HEAD 2004-06-19 07:27:27 UTC
gdb drow_intercu-20040221-branch 2004-06-19 07:35:36 UTC
gdb gdb_6_1-branch 2004-06-19 07:39:10 UTC
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
dejagnu => dejagnu 1.4.4
expect => expect 5.41
tcl => tcl 8.4.6
gdb => 6.1.1, gdb_6_1-branch, HEAD, drow_intercu-20040221-branch
suite => 6.1.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 3.3.4-20040530, gcc 3.3.4, gcc gcc-3_3-branch, gcc 3.4.0, gcc 3.4.1-20040625, gcc 3.4.1, gcc gcc-3_4-branch, gcc HEAD
as => binutils 2.13.90.0.2-rh, binutils 2.15, binutils binutils-2_15-branch, binutils HEAD
ld => binutils 2.13.90.0.2-rh, binutils 2.15, binutils binutils-2_15-branch, binutils HEAD
libc => glibc 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count => 266
'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 gdb 6.1.1 suite 6.1.1, 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.15 + ld
binutils 2.15.
. Host Software
. host=i686-pc-linux-gnu, osversion=red-hat-8.0
make 3.79.1
binutils 2.14
gcc 3.3.3
flex 2.5.4
bison 1.875
texinfo 4.7
tcl 8.4.6
expect 5.41
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 gdb 6.1.
I dropped gdb 6.1.0.95.
I added gcc 3.3.4.
I added gcc 3.4.1-20040625.
I added gcc 3.4.1.
This is the last spin for gdb gdb_6_1-branch.
The next spin will cover gdb gdb_6_2-branch.
This is the last spin for gcc 3.3.3.
This is the last spin for gcc 3.3.4-20040530.
This is the last spin for gcc 3.4.0.
This is the last spin for gcc 3.4.1-20040625.
This is the last spin for binutils binutils-2_15-branch.