This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-06-30
- 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: Tue, 1 Jul 2003 21:36:22 -0400
- Subject: sunday project, gdb, 2003-06-30
Highlights of this report:
. libiberty added some new tests which reveal existing demangler bugs.
Michael C
. Old Bugs Fixed
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10718
nested locals with same name broken with gcc HEAD 2003-04-11
http://sources.redhat.com/gdb/bugs/1180
nested locals with same name broken with gcc HEAD 2003-04-11
. New Bugs Detected
None.
. PR Count
Query executed 2003-07-02T01:27:12Z
1268 matches found
17 analyzed
577 closed
21 feedback
639 open
3 paperwork
11 suspended
1268 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.2.3, binutils binutils-2_14-branch All 648 tests passed
gcc 3.2.3, binutils HEAD All 648 tests passed
gcc 3.3, binutils binutils-2_14-branch 649 tests, 0 failures
gcc 3.3, 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
There are new failures in this report from new tests for the C++
demangler. The demangler has not changed at all. H. J. Lu wrote
some new tests which reveal existing bugs. Libiberty testing does
not use dejagnu, but if it did, these would be KFAIL's.
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
One of my libiberty logs 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-06-30/index.html
The previous report was 2003-06-25:
http://www.shout.net/~mec/sunday/2003-06-25/Analysis.txt
. Non-PASS Results
gdb 5.3: 0 test aborts, 418 non-PASS results
gdb gdb_6_0-branch: 0 test aborts, 434 non-PASS results
gdb HEAD: 0 test aborts, 435 non-PASS results
. 5.3
. gdb.base/scope.exp: print localval, outer scope
gdb.mi/mi-var-block.exp: create local variable foo
gdb.mi/mi-var-block.exp: delete var foo
gdb.mi/mi0-var-block.exp: create local variable foo
gdb.mi/mi0-var-block.exp: delete var foo
FAIL -> PASS
Zack W fixed a bug in gcc.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10718
nested locals with same name broken with gcc HEAD 2003-04-11
http://sources.redhat.com/gdb/bugs/1180
nested locals with same name broken with gcc HEAD 2003-04-11
. 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.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/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-06-30 20:00:44 UTC'
. gdb.base/scope.exp: print localval, outer scope
gdb.mi/mi-var-block.exp: create local variable foo
gdb.mi/mi-var-block.exp: delete var foo
gdb.mi/mi1-var-block.exp: create local variable foo
gdb.mi/mi1-var-block.exp: delete var foo
FAIL -> PASS
Same analysis as 5.3.
. gdb.base/selftest.exp: step into xmalloc call
FAIL -> PASS
gdb.base/selftest.exp: next over dirsize initialization
null -> PASS
Michael C and Daniel J fixed bugs in the test script.
. gdb.c++/annota2.exp: annotate-quit
Same analysis as 5.3.
. gdb.c++/maint.exp: set complaints -1
gdb.c++/maint.exp: maint cp first_component foo<
gdb.c++/maint.exp: maint cp first_component foo(
gdb.c++/maint.exp: maint cp first_component bool operator<<char>
null -> PASS
David C wrote some new tests.
All tests PASSed in all configurations.
. 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
null -> PASS
PASS -> null
Fluctuation due to unknown causes. Probably harmless.
. gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
Same analysis as 5.3.
. gdb.threads/linux-dp.exp: philosopher is distinct: 6
gdb.threads/linux-dp.exp: philosopher is distinct: 7
FAIL -> PASS
PASS -> FAIL
These tests are sensitive to a backtrace bug in gdb. If a
thread is waiting on 'select', then gdb prints a deficient
backtrace, and the test FAILs.
http://sources.redhat.com/gdb/bugs/1255
[regression] bad backtrace for libc function 'sleep'
. gdb.threads/print-threads.exp: Running threads (slow with kill breakpoint)
FAIL -> KFAIL
Daniel J added a KFAIL for this.
http://sources.redhat.com/gdb/bugs/1265
GNU/Linux LWP layer gets confused when thread-db says a thread has exited
. 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 5 37
thread 1 33 9
thread 2 38 4
thread 3 41 1
thread 4 41 1
thread 5 42 0
. gdb HEAD
checkout date is '2003-06-30 19:57:20 UTC'
. gdb.base/completion.exp: complete 'file ./gdb.base/compl'
PASS -> null
gdb.base/completion.exp: complete 'file ./gdb.base/complet'
null -> PASS
Daniel J changed the test -- there is now a second test that
starts with 'compl'.
. gdb.base/complex.exp: print complex packed value in C
null -> XFAIL
null -> FAIL
null -> PASS
gdb.base/complex.exp: print complex value in C
null -> PASS
null -> FAIL
Daniel J wrote a new test script.
Results for the packed test:
dwarf-2 stabs+
gcc 2.95.3 XFAIL pass
gcc 3.2-7-rh pass FAIL
gcc 3.2.3 pass pass
gcc 3.3 pass pass
gcc gcc-3_3-branch pass pass
gcc HEAD pass pass
Results for the not-packed test:
dwarf-2 stabs+
gcc 2.95.3 pass pass
gcc 3.2-7-rh pass FAIL
gcc 3.2.3 pass pass
gcc 3.3 pass pass
gcc gcc-3_3-branch pass pass
gcc HEAD pass pass
The XFAIL is expected, but the FAILs are not.
gcc 3.2-7-rh is the vendor compiler with red hat linux 8. Elena
Z has results for gcc 3.2.2-5-rh on red hat linux 9, but they
don't include the new test yet. I have made a note to look at
these results when they are available.
. gdb.base/constvars.exp: ptype crisp
gdb.base/constvars.exp: ptype l*
gdb.base/volatile.exp: ptype c*
gdb.base/volatile.exp: ptype v*
XPASS -> PASS
This happened with gcc 3.X -gstabs+.
Daniel J removed obsolete setup_xfail calls from the test
script.
. gdb.base/scope.exp: print localval, outer scope
gdb.mi/mi-var-block.exp: create local variable foo
gdb.mi/mi-var-block.exp: delete var foo
gdb.mi/mi1-var-block.exp: create local variable foo
gdb.mi/mi1-var-block.exp: delete var foo
FAIL -> PASS
Same analysis as 5.3.
. gdb.base/selftest.exp: step into xmalloc call
FAIL -> PASS
gdb.base/selftest.exp: next over dirsize initialization
null -> PASS
Same analysis as gdb_6_0-branch.
. gdb.c++/annota2.exp: annotate-quit
Same analysis as 5.3.
. gdb.c++/inherit.exp: print g_vB
gdb.c++/inherit.exp: print g_vC
gdb.c++/inherit.exp: print g_vD
FAIL -> PASS
This happened with gcc 3.3 -gstabs+ and gcc gcc-3_3-branch
-gstabs+.
Michael C improved the test script to accept the gdb output with
newer versions of gcc.
. gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
Same analysis as 5.3.
. gdb.c++/maint.exp: set complaints -1
gdb.c++/maint.exp: maint cp first_component foo<
gdb.c++/maint.exp: maint cp first_component foo(
gdb.c++/maint.exp: maint cp first_component bool operator<<char>
null -> PASS
Same analysis as 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
null -> PASS
PASS -> null
Same analysis as gdb_6_0-branch.
. gdb.threads/linux-dp.exp: philosopher is distinct: 3
gdb.threads/linux-dp.exp: philosopher is distinct: 4
gdb.threads/linux-dp.exp: philosopher is distinct: 6
gdb.threads/linux-dp.exp: philosopher is distinct: 7
FAIL -> PASS
PASS -> FAIL
Same analysis as gdb_6_0-branch.
. gdb.threads/print-threads.exp: Running threads (slow with kill breakpoint)
FAIL -> KFAIL
Same analysis as gdb_6_0-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 8 34
thread 1 36 6
thread 2 39 3
thread 3 42 0
thread 4 38 4
thread 5 42 0
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
gdb => 5.3, gdb_6_0-branch%20030630, HEAD%20030630
gcc => 2.95.3, 3.2-7-rh, 3.2.3, 3.3, gcc-3_3-branch%20030629, HEAD%20030629
binutils => 2.13.90.0.2-rh, 2.14, binutils-2_14-branch%20030629, HEAD%20030629
glibc => 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count 126 = 1 * 1 * 1 * 3 * (5*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.
cvs versions (head and branch) show the checkout date after a '%' delimiter.
'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 '(5*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.2.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.5.1.tar.gz
ftp://ftp.shout.net/pub/users/mec/Migbat/Migbat-0.5.1.tar.gz
. Test Bed Changes Since Last Report
I upgraded host binutils from 2.13.2.1 to 2.14. This is the binutils
that I use to build gdb (and other things), not the binutils that I
use to build the test programs.
I upgraded host gcc from 3.2.2 to 3.2.3.
I upgraded host tcl from 8.4.1 to 8.4.3.