This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-09-18
- From: Michael Elizabeth Chastain <mec at shout dot net>
- To: gcc-testresults at gcc dot gnu dot org, gdb-testers at sources dot redhat dot com
- Date: Fri, 19 Sep 2003 20:48:55 -0400
- Subject: sunday project, gdb, 2003-09-18
. Highlights of this report
gdb gdb_6_0-branch is fine as of 2003-09-18 15:29:30 UTC.
The killer bug with g++ HEAD -gstabs+ has been fixed.
Michael C
. Old Bugs Fixed
. gcc HEAD
Mark M fixed a critical bug:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12066
g++ generates stabs for "char *" that gdb cannot read
. New Bugs Detected
. gdb 5.3
One instance of this popped up:
Cannot find thread 8192: generic error
. PR Count
Query executed 2003-09-16 23:02:17 UTC
1384 matches found
21 analyzed
642 closed
24 feedback
684 open
3 paperwork
10 suspended
1384 TOTAL
. Libiberty Testing
. target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
binutils HEAD 714 tests, 31 failures
gcc 2.95.3, binutils HEAD All 616 tests passed
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 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 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-09-18/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2003-09-15/index.html
. Non-PASS Results
gdb 5.3 338 non-PASS results
gdb 5.3.92 313 non-PASS results
gdb gdb_6_0-branch 315 non-PASS results
gdb HEAD 350 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 improved with gcc HEAD -gstabs+.
Mark M fixed a bug in gcc HEAD:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12066
g++ generates stabs for "char *" that gdb cannot read
. gdb.c++/virtfunc.exp: ptype VA
UNRESOLVED -> PASS
This was 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/pthreads.exp: backtrace from thread 2 bkpt in common_routine
PASS -> blank
gdb.threads/pthreads.exp: continue to bkpt at common_routine in thread 2
PASS -> FAIL
This happened in just one configuration. gdb.log excerpt:
(gdb) PASS: gdb.threads/pthreads.exp: apply backtrace command to all three threads
# gdb 5.3, gcc HEAD, binutils vendor, stabs+
break common_routine thread 4
Breakpoint 6 at 0x804858a: file /berman/migchain/source/gdb-5.3/gdb/testsuite/gdb.threads/pthreads.c, line 51.
(gdb) PASS: gdb.threads/pthreads.exp: set break at common_routine in thread 2
continue
Continuing.
Cannot find thread 8192: generic error
(gdb) FAIL: gdb.threads/pthreads.exp: continue to bkpt at common_routine in thread 2
testcase /berman/migchain/source/gdb-5.3/gdb/testsuite/gdb.threads/pthreads.exp completed in 3 seconds
It didn't happen when I ran the configuration again. So I am
throwing this on the "unexplained mysteries" pile.
. 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
. 5.3.92
. gdb.cp/cplusfuncs.exp: info function for "operator char\*("
gdb.cp/local.exp: *
gdb.cp/m-data.exp: *
gdb.cp/m-static.exp: *
gdb.cp/namespace.exp: info func xyzq
gdb.cp/namespace.exp: print 'BBB::Class::xyzq'
gdb.cp/overload.exp: *
gdb.cp/ref-types.exp: *
gdb.cp/templates.exp: print *
gdb.cp/templates.exp: ptype *
gdb.cp/try_catch.exp: *
gdb.cp/userdef.exp: *
gdb.mi/gdb792.exp: list children of A.private
gdb.mi/gdb792.exp: list children of A.public
Same analysis as gdb 5.3.
. gdb.cp/virtfunc.exp: ptype VA
UNRESOLVED -> PASS
Same analysis as gdb 5.3.
. 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 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 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.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 24
thread 1 25 1
thread 2 25 1
thread 3 26 0
thread 4 26 0
thread 5 26 0
. gdb gdb_6_0-branch
checkout date is '2003-09-18 15:29:30 UTC'
previous date is '2003-09-15 20:53:09 UTC'
. gdb.cp/annota2.exp: annotate-quit
gdb.cp/annota3.exp: annotate-quit
http://sources.redhat.com/gdb/bugs/544
gdb.c++/annota2.exp: annotate-quit test sometimes fails
Same analysis as gdb 5.3.
. gdb.cp/cplusfuncs.exp: info function for "operator char\*("
gdb.cp/local.exp: *
gdb.cp/m-data.exp: *
gdb.cp/m-static.exp: *
gdb.cp/namespace.exp: info func xyzq
gdb.cp/namespace.exp: print 'BBB::Class::xyzq'
gdb.cp/overload.exp: *
gdb.cp/ref-types.exp: *
gdb.cp/templates.exp: print *
gdb.cp/templates.exp: ptype *
gdb.cp/try_catch.exp: *
gdb.cp/userdef.exp: *
gdb.mi/gdb792.exp: list children of A.private
gdb.mi/gdb792.exp: list children of A.public
Same analysis as gdb 5.3.
. gdb.cp/virtfunc.exp: ptype VA
UNRESOLVED -> PASS
Same analysis as gdb 5.3.
. 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 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
blank -> PASS
PASS -> blank
Same analysis as gdb 5.3.92.
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
blank -> PASS
Same analysis as gdb 5.3.92.
. 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 6 20
thread 1 21 5
thread 2 25 1
thread 3 24 2
thread 4 25 1
thread 5 26 0
. gdb HEAD
checkout date is '2003-09-18 15:26:46 UTC'
previous date is '2003-09-15 20:48:44 UTC'
. gdb.cp/cplusfuncs.exp: info function for "operator char\*("
gdb.cp/local.exp: *
gdb.cp/m-data.exp: *
gdb.cp/m-static.exp: *
gdb.cp/namespace.exp: info func xyzq
gdb.cp/namespace.exp: print 'BBB::Class::xyzq'
gdb.cp/overload.exp: *
gdb.cp/ref-types.exp: *
gdb.cp/templates.exp: print *
gdb.cp/templates.exp: ptype *
gdb.cp/try_catch.exp: *
gdb.cp/userdef.exp: *
gdb.mi/gdb792.exp: list children of A.private
gdb.mi/gdb792.exp: list children of A.public
Same analysis as gdb 5.3.
. gdb.cp/virtfunc.exp: ptype VA
UNRESOLVED -> PASS
Same analysis as gdb 5.3.
. gdb.cp/gdb1355.exp: print s1
gdb.cp/gdb1355.exp: ptype s1
blank -> PASS
Michael C wrote a new test script.
. 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 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 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
Same analysis as gdb 5.3.92.
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
blank -> PASS
Same analysis as gdb 5.3.92.
. 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 23
thread 1 23 3
thread 2 25 1
thread 3 26 0
thread 4 25 1
thread 5 26 0
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
gdb => 5.3, 5.3.92, 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, HEAD
glibc => 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count 104 = 1 * 1 * 1 * 4 * (4*3+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*3+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.4
expect 5.39
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 Gnu 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
I dropped target gdb 5.3.91.