This is the mail archive of the
gcc-testresults@gcc.gnu.org
mailing list for the GCC project.
sunday project, gdb, 2003-10-22
- 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: Thu, 23 Oct 2003 14:32:31 -0400
- Subject: sunday project, gdb, 2003-10-22
. Highlights of this report
No new bugs detected.
The current tables are always at
http://www.shout.net/~mec/sunday/current/index.html
Michael C
. Old Bugs Fixed
http://sources.redhat.com/gdb/bugs/1405
regression: print pEe->vd(), virtual baseclass botch, g++ 2.95.3 -gdwarf-2
This bug does not happen with binutils HEAD. It still happens with
vendor binutils and binutils 2.14.
. New Bugs Detected
None.
. PR Count
Query executed 2003-10-23 18:14:11 UTC
1426 matches found
22 analyzed
650 closed
22 feedback
719 open
3 paperwork
10 suspended
1426 TOTAL
. Libiberty Testing
. target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
binutils HEAD 715 tests, 31 failures
gcc 2.95.3, binutils HEAD All 616 tests passed
gcc 3.3.2, 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 715 tests, 31 failures
gcc HEAD, binutils HEAD 715 tests, 31 failures
gcc HEAD, binutils vendor 715 tests, 31 failures
gdb HEAD 715 tests, 31 failures
gdb carlton_dictionary-branch 714 tests, 31 failures
gdb gdb_6_0-branch 649 tests, 0 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-10-22/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2003-10-18/index.html
. Non-PASS Results
gdb 6.0 311 non-PASS results
gdb gdb_6_0-branch 314 non-PASS results
gdb HEAD 360 non-PASS results
. 6.0
. gdb.base/selftest.exp: next over dirsize initialization
gdb.base/selftest.exp: next over ncmd initialization
gdb.base/selftest.exp: next over corearg initialization
blank -> PASS
This change is benign. I upgraded the host gcc in my test bed
from gcc 3.3.1 to gcc 3.3.2. selftest.exp operates on the gdb
executable, so it is sensitive to the host gcc version.
. gdb.cp/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.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, the
thread library in the inferior program behaves differently: it
generates more signals so that gdb can track events.
This causes some programs to behave differently because they
aren't prepared to handle the additional signals. 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 0 26
thread 1 26 0
thread 2 26 0
thread 3 26 0
thread 4 26 0
thread 5 26 0
. gdb gdb_6_0-branch
checkout date is '2003-10-22 14:44:46 UTC'
previous date is '2003-10-18 16:13:27 UTC'
. gdb.base/selftest.exp: next over dirsize initialization
gdb.base/selftest.exp: next over ncmd initialization
gdb.base/selftest.exp: next over corearg initialization
blank -> PASS
Same analysis as gdb 6.0.
. gdb.cp/annota2.exp: annotate-quit
gdb.cp/annota3.exp: annotate-quit
Same analysis as gdb 6.0.
. gdb.mi/mi*-pthreads.exp: check mi_thread_command_set: -thread-select [3456]
PASS -> blank
blank -> PASS
Same analysis as gdb 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 5 21
thread 1 21 5
thread 2 24 2
thread 3 25 1
thread 4 26 0
thread 5 26 0
. gdb HEAD
checkout date is '2003-10-22 14:42:25 UTC'
previous date is '2003-10-18 16:11:16 UTC'
. gdb.base/gdb1056.exp: print 1/0
blank -> KFAIL
Michael C wrote a new test which exposes an existing bug in gdb.
. gdb.base/selftest.exp: next over dirsize initialization
gdb.base/selftest.exp: next over ncmd initialization
gdb.base/selftest.exp: next over corearg initialization
blank -> PASS
Same analysis as gdb 6.0.
. gdb.cp/annota2.exp: annotate-quit
gdb.cp/annota3.exp: annotate-quit
Same analysis as gdb 6.0.
. gdb.cp/virtfunc.exp: print pEe->vd()
FAIL -> PASS
There is a PR for this:
http://sources.redhat.com/gdb/bugs/1405
regression: print pEe->vd(), virtual baseclass botch, g++ 2.95.3 -gdwarf-2
This test PASSed with binutils HEAD.
It still FAILed with vendor binutils and binutils 2.14.
. gdb.mi/mi*-pthreads.exp: check mi_thread_command_set: -thread-select [3456]
blank -> PASS
PASS -> blank
Same analysis as gdb 6.0.
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
PASS -> blank
Same analysis as gdb 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 3 23
thread 1 24 2
thread 2 25 1
thread 3 26 0
thread 4 26 0
thread 5 26 0
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
gdb => 6.0, gdb_6_0-branch, HEAD
gcc => 2.95.3, 3.2-7-rh, 3.3.2, 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 78 = 1 * 1 * 1 * 3 * (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.2
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.7.tar.gz
ftp://ftp.shout.net/pub/users/mec/migbat/migbat-0.7.tar.gz
. Test Bed Changes Since Last Report
I dropped target gcc 3.3.1 and target gcc 3.3.2-20031007.
I upgraded the host gcc from gcc 3.3.1 to gcc 3.3.2. This is the gcc
for building gdb itself, not the gcc used for building test programs.
I released migchain 0.7 and migbat 0.7.
In the release announcement for gcc 3.3.2, Mark Mitchell said that he
doesn't plan any more releases from gcc-3_3-branch. But there is
still a little activity on the branch, so I am still covering it.