This is the mail archive of the
gcc-testresults@gcc.gnu.org
mailing list for the GCC project.
sunday project, gdb, 2003-11-30
- 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: Sun, 30 Nov 2003 18:02:09 -0500 (EST)
- Subject: sunday project, gdb, 2003-11-30
. Highlights of This Spin
All is calm.
The last ChangeLog entry on gdb gdb_6_0-branch was 2003-10-29, more
than a month ago. Until I see activity on this branch I am going to
drop coverage of this branch.
The current tables are always at:
http://www.shout.net/~mec/sunday/current/index.html
Michael C
. Old Bugs Fixed
None.
. New Bugs Detected
None.
. PR Count
Query executed 2003-11-30 22:18:27 UTC
1470 matches found
24 analyzed
663 closed
20 feedback
750 open
3 paperwork
10 suspended
1470 TOTAL
. Libiberty Testing
. target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
binutils HEAD 721 tests, 1 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 721 tests, 1 failures
gcc HEAD, binutils HEAD 721 tests, 1 failures
gcc HEAD, binutils vendor 721 tests, 1 failures
gdb HEAD 721 tests, 1 failures
gdb carlton_dictionary-branch 715 tests, 31 failures
gdb gdb_6_0-branch 649 tests, 0 failures
Ian L-T fixed some more bugs in the demangler and added 2 more
tests. There were no regressions in the demangler test suite.
I keep some libiberty logs at:
http://www.shout.net/~mec/sunday/libiberty/2003-11-29.log
http://www.shout.net/~mec/sunday/libiberty/2003-11-25.log
http://www.shout.net/~mec/sunday/libiberty/2003-11-21.log
http://www.shout.net/~mec/sunday/libiberty/2003-06-30.log
. Gdb Testing
My tables are at
http://www.shout.net/~mec/sunday/2003-11-30/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2003-11-26/index.html
. Non-PASS Results
gdb 6.0 318 non-PASS results
gdb gdb_6_0-branch 317 non-PASS results
gdb HEAD 413 non-PASS results
. gdb 6.0
. 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, gdb uses
hidden breakpoints in the thread library to track events such as
thread creation and thread destruction.
This causes some programs to behave differently because they
aren't prepared to handle the additional signals caused by the
hidden breakpoints. 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 2 24
thread 1 26 0
thread 2 24 2
thread 3 25 1
thread 4 26 0
thread 5 26 0
. gdb gdb_6_0-branch
checkout date is '2003-11-30 06:10:21 UTC'
previous date is '2003-11-26 07:44:27 UTC'
. 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]
PASS -> blank
blank -> PASS
Same analysis as gdb 6.0.
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
PASS -> blank
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 22
thread 1 22 4
thread 2 26 0
thread 3 26 0
thread 4 26 0
thread 5 26 0
. gdb HEAD
checkout date is '2003-11-30 06:08:24 UTC'
previous date is '2003-11-26 07:42:26 UTC'
. gdb.cp/annota2.exp: annotate-quit
gdb.cp/annota3.exp: annotate-quit
Same analysis as gdb gdb_6_0-branch.
. gdb.objc/objcdecode.exp: continue after break on multiply defined symbol
FAIL -> blank
blank -> FAIL
gdb.objc/objcdecode.exp: continue after break on multiply defined symbol (timeout)
blank -> FAIL
FAIL -> blank
The test script has some bad regular expressions which
desynchronize dejagnu. I submitted a patch to fix this:
http://sources.redhat.com/ml/gdb-patches/2003-11/msg00612.html
[rfc/testsuite/objc] objcdecode.exp: fix and clean up
. 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 1 25
thread 1 26 0
thread 2 26 0
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 => 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
None.