This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-08-23
- From: Michael Elizabeth Chastain <mec at shout dot net>
- To: gcc-testresults at sources dot redhat dot com, gdb-testers at sources dot redhat dot com
- Date: Wed, 27 Aug 2003 00:24:21 -0400
- Subject: sunday project, gdb, 2003-08-23
. Highlights of this report
Mark K fixed a backtrace bug, pr gdb/1338.
gcc HEAD has a new bug with g++ -gstabs+, pr gcc/12066.
Michael C
. Old Bugs Fixed
. gdb gdb_6_0-branch
http://sources.redhat.com/gdb/bugs/1338
can't backtrace through select()
Mark K fixed it.
. gdb HEAD
http://sources.redhat.com/gdb/bugs/1338
can't backtrace through select()
Mark K fixed it.
. New Bugs Detected
. gcc HEAD
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12066
g++ generates stabs for "char *" that gdb cannot read
. PR Count
Query executed 2003-08-27T04:15:54Z
1355 matches found
21 analyzed
609 closed
28 feedback
683 open
3 paperwork
11 suspended
1355 TOTAL
. Libiberty Testing
. target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
binutils binutils-2_14-branch 649 tests, 0 failures
binutils HEAD 714 tests, 31 failures
gcc 2.95.3, binutils binutils-2_14-branch All 616 tests passed
gcc 2.95.3, binutils HEAD All 616 tests passed
gcc 3.3.1, binutils binutils-2_14-branch 649 tests, 0 failures
gcc 3.3.1, binutils HEAD 649 tests, 0 failures
gcc gcc-3_3-branch, binutils 2.14 649 tests, 0 failures
gcc gcc-3_3-branch, binutils binutils-2_14-branch 649 tests, 0 failures
gcc gcc-3_3-branch, binutils HEAD 649 tests, 0 failures
gcc gcc-3_3-branch, binutils vendor 649 tests, 0 failures
gcc HEAD, binutils 2.14 714 tests, 31 failures
gcc HEAD, binutils binutils-2_14-branch 714 tests, 31 failures
gcc HEAD, binutils HEAD 714 tests, 31 failures
gcc HEAD, binutils vendor 714 tests, 31 failures
gdb carlton_dictionary-branch 714 tests, 31 failures
gdb gdb_6_0-branch 649 tests, 0 failures
gdb HEAD 714 tests, 31 failures
These are long-standing demangler bugs.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7986
Problems with demangling (__cxa_demangle())
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11028
The standalone C++ demangler doesn't work on some symbols
A libiberty log is available at
http://gcc.gnu.org/ml/gcc/2003-07/msg00032.html
. Gdb Testing
My tables are at
http://www.shout.net/~mec/sunday/2003-08-23/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2003-08-16/index.html
. Non-PASS Results
gdb 5.3 427 non-PASS results
gdb gdb_6_0-branch 406 non-PASS results
gdb HEAD 441 non-PASS results
. 5.3
. gdb.c++/annota2.exp: annotate-quit
http://sources.redhat.com/gdb/bugs/544
gdb.c++/annota2.exp: annotate-quit test sometimes fails
Fluctuation in test result probably due to a signal handling
race in the command loop.
. gdb.c++/cplusfuncs.exp: info function for "operator char\*("
gdb.c++/local.exp: *
gdb.c++/m-data.exp: *
gdb.c++/m-static.exp: *
gdb.c++/namespace.exp: info func xyzq
gdb.c++/namespace.exp: print 'BBB::Class::xyzq'
gdb.c++/overload.exp: *
gdb.c++/ref-types.exp: *
gdb.c++/templates.exp: ptype *
gdb.c++/try_catch.exp: *
gdb.c++/userdef.exp: *
These tests regressed with gcc HEAD -gstabs+.
This is new a bug in gcc HEAD
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12066
g++ generates stabs for "char *" that gdb cannot read
Special props to try_catch.exp and userdef.exp for causing
gdb to segfault on "break main". Those are good test
scripts! Unfortunately, I have no time to analyze the bugs
in gdb which cause it crash with funky stabs.
. gdb.c++/virtfunc.exp: ptype VA
PASS -> UNRESOLVED
This is just a cascade problem from the previous test script,
gdb.c++/userdef.exp.
. gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
http://sources.redhat.com/gdb/bugs/568
GDB confused by messily-exiting multi-threaded programs
Jim B thinks that this test may depend on a race condition:
http://sources.redhat.com/ml/gdb-testers/2002-q4/msg00010.html
. gdb.threads/print-threads.exp: Hit kill breakpoint, 9 (slow with kill breakpoint)
gdb.threads/print-threads.exp: Hit kill breakpoint, 10 (slow with kill breakpoint)
blank -> PASS
Fluctuation with unknown cause. Probably harmless.
. gdb.threads/schedlock.exp: *
This test script is useless in this release because of a
signed-versus-unsigned bug.
Daniel J has an obvious fix, which has been applied to gdb HEAD:
http://sources.redhat.com/ml/gdb-patches/2002-10/msg00454.html
. gdb_6_0-branch
checkout date is '2003-08-24 00:22:36 UTC'
previous date is '2003-08-16 19:52:12 UTC'
. gdb.c++/annota2.exp: annotate-quit
gdb.c++/annota3.exp: annotate-quit
Same analysis as gdb 5.3.
. gdb.c++/cplusfuncs.exp: info function for "operator char\*("
gdb.c++/local.exp: *
gdb.c++/m-data.exp: *
gdb.c++/m-static.exp: *
gdb.c++/namespace.exp: info func xyzq
gdb.c++/namespace.exp: print 'BBB::Class::xyzq'
gdb.c++/overload.exp: *
gdb.c++/ref-types.exp: *
gdb.c++/templates.exp: ptype *
gdb.c++/try_catch.exp: *
gdb.c++/userdef.exp: *
gdb.mi/gdb792.exp: list children of A.public
gdb.mi/gdb792.exp: list children of A.private
Same analysis as gdb 5.3.
. gdb.c++/virtfunc.exp: ptype VA
PASS -> UNRESOLVED
Same analysis as gdb 5.3.
. gdb.java/jmisc.exp: *
gdb.java/jmisc1.exp: *
* -> *
In the previous report, one configuration blew up on these
two java test scripts: gdb gdb_6_0-branch, gcc HEAD, binutils 2.14,
gformat stabs+. The cause was a genuine timeout, gjc actually
taking more time than allotted to run, because the tests ran
at the same time as a 4:00 AM cron job.
These tests are back to normal on this report.
. gdb.mi/mi-pthreads-exp: check mi_thread_command_set: -thread-select 3
gdb.mi/mi-pthreads-exp: check mi_thread_command_set: -thread-select 4
gdb.mi/mi-pthreads-exp: check mi_thread_command_set: -thread-select 5
gdb.mi/mi-pthreads-exp: check mi_thread_command_set: -thread-select 6
gdb.mi/mi1-pthreads-exp: check mi_thread_command_set: -thread-select 3
gdb.mi/mi1-pthreads-exp: check mi_thread_command_set: -thread-select 4
gdb.mi/mi1-pthreads-exp: check mi_thread_command_set: -thread-select 5
gdb.mi/mi1-pthreads-exp: check mi_thread_command_set: -thread-select 6
gdb.mi/mi2-pthreads-exp: check mi_thread_command_set: -thread-select 3
gdb.mi/mi2-pthreads-exp: check mi_thread_command_set: -thread-select 4
gdb.mi/mi2-pthreads-exp: check mi_thread_command_set: -thread-select 5
gdb.mi/mi2-pthreads-exp: check mi_thread_command_set: -thread-select 6
PASS -> blank
blank -> PASS
Fluctuation with unknown cause. Probably harmless.
. gdb.mi/mi-var-display.exp: get children local variable weird
gdb.mi/mi1-var-display.exp: get children local variable weird
gdb.mi/mi2-var-display.exp: get children local variable weird
FAIL -> PASS
Daniel J improved the test script.
. gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
Same analysis as gdb 5.3.
. gdb.threads/linux-dp.exp: philosopher is distinct: 3
gdb.threads/linux-dp.exp: philosopher is distinct: 6
gdb.threads/linux-dp.exp: philosopher is distinct: 7
FAIL -> PASS
Mark K fixed a bug in gdb.
http://sources.redhat.com/gdb/bugs/1338
can't backtrace through select()
. gdb.threads/print-threads.exp: Hit kill breakpoint, 10 (slow with kill breakpoint)
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 4 30
thread 1 28 6
thread 2 34 0
thread 3 33 1
thread 4 34 0
thread 5 34 0
. gdb HEAD
checkout date is '2003-08-24 00:19:35 UTC'
previous date is '2003-08-16 19:47:28 UTC'
. gdb.arch/i386-prologue.exp: continue to gdb1338
gdb.arch/i386-prologue.exp: backtrace in gdb1338
blank -> PASS
Mark K wrote some sweet new tests.
. gdb.base/annota3.exp: annotate ignore count change
FAIL -> PASS
Daniel J fixed a bug in the test script.
. gdb.c++/annota2.exp: annotate-quit
gdb.c++/annota3.exp: annotate-quit
Same analysis as gdb 5.3.
. gdb.c++/cplusfuncs.exp: info function for "operator char\*("
gdb.c++/local.exp: *
gdb.c++/m-data.exp: *
gdb.c++/m-static.exp: *
gdb.c++/namespace.exp: info func xyzq
gdb.c++/namespace.exp: print 'BBB::Class::xyzq'
gdb.c++/overload.exp: *
gdb.c++/ref-types.exp: *
gdb.c++/templates.exp: ptype *
gdb.c++/try_catch.exp: *
gdb.c++/userdef.exp: *
gdb.mi/gdb792.exp: list children of A.public
gdb.mi/gdb792.exp: list children of A.private
Same analysis as gdb 5.3.
. gdb.java/jmisc.exp: *
gdb.java/jmisc1.exp: *
gdb.java/jmisc2.exp: *
Java compilation timeout. This is a deficiency in my test bed.
. gdb.mi/mi-var-display.exp: get children local variable weird
gdb.mi/mi1-var-display.exp: get children local variable weird
gdb.mi/mi2-var-display.exp: get children local variable weird
FAIL -> PASS
Same analysis as gdb gdb_6_0-branch.
. gdb.mi/mi-pthreads-exp: check mi_thread_command_set: -thread-select 3
gdb.mi/mi-pthreads-exp: check mi_thread_command_set: -thread-select 4
gdb.mi/mi-pthreads-exp: check mi_thread_command_set: -thread-select 5
gdb.mi/mi-pthreads-exp: check mi_thread_command_set: -thread-select 6
gdb.mi/mi1-pthreads-exp: check mi_thread_command_set: -thread-select 3
gdb.mi/mi1-pthreads-exp: check mi_thread_command_set: -thread-select 4
gdb.mi/mi1-pthreads-exp: check mi_thread_command_set: -thread-select 5
gdb.mi/mi1-pthreads-exp: check mi_thread_command_set: -thread-select 6
gdb.mi/mi2-pthreads-exp: check mi_thread_command_set: -thread-select 5
gdb.mi/mi2-pthreads-exp: check mi_thread_command_set: -thread-select 6
blank -> PASS
PASS -> blank
Same analysis as gdb gdb_6_0-branch.
. gdb.threads/linux-dp.exp: philosopher is distinct: 6
gdb.threads/linux-dp.exp: philosopher is distinct: 7
FAIL -> PASS
Same analysis as gdb gdb_6_0-branch.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
PASS -> BLANK
Same analysis as gdb gdb_6_0-branch.
Except this one goes to 11.
. 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 32
thread 1 26 8
thread 2 34 0
thread 3 34 0
thread 4 33 1
thread 5 34 0
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
gdb => 5.3, gdb_6_0-branch, HEAD
gcc => 2.95.3, 3.2-7-rh, 3.3.1, gcc-3_3-branch, HEAD
binutils => 2.13.90.0.2-rh, 2.14, binutils-2_14-branch, HEAD
glibc => 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count 102 = 1 * 1 * 1 * 3 * (4*4+1*1) * 1 * 2 * 1
'target' and 'host' are gnu configuration triples.
'osversion' is the host operating system name, which is additional
information beyond 'host'.
'gdb', 'gcc', 'binutils', and 'glibc' are version 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.
The vendor gcc is available only with vendor binutils,
thus the '(4*4+1*1)' term for gcc/binutils combinations.
. Host Software
. host=i686-pc-linux-gnu, osversion=red-hat-8.0
make 3.79.1
binutils 2.14
gcc 3.3
flex 2.5.4
bison 1.875
tcl 8.4.3
expect 5.38.0
dejagnu 1.4.3
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 Build and Test), and they are licensed under the
GPL.
ftp://ftp.shout.net/pub/users/mec/migchain/migchain-0.6.tar.gz
ftp://ftp.shout.net/pub/users/mec/migbat/migbat-0.6.tar.gz
. Test Bed Changes Since Last Report
The gdb testsuite renamed all the c++ tests from gdb.c++ to gdb.cp.
My results-cruncher accommodates this by fuzzing both 'gdb.c++' and
'gdb.cp' to 'gdb.cp.c++', so that I can match test names across the
name change. This is similar to the 'gdb.mi/mi0-*' and 'gdb.mi/mi1-*'
comparison, which I accommodate by fuzzing both names to
'gdb.mi/mi[01]-*'.