This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-01-20
- From: Michael Elizabeth Chastain <mec at shout dot net>
- To: gdb-testers at sources dot redhat dot com
- Date: Tue, 21 Jan 2003 15:35:25 -0600
- Subject: sunday project, gdb, 2003-01-20
Highlights of this report:
. No new bugs detected.
. The new sources.redhat.com does checkouts in about 1/2 the time of
the old machine. But my measurements do not take account of the load
factor on the server, or of fluctuations I have on my DSL connection.
My tables are here:
http://www.shout.net/~mec/sunday/2003-01-20/index.html
Michael C
. Old Bugs Fixed
None.
. New Bugs Detected
None.
. Libiberty Testing
. target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
binutils HEAD 649 tests, 0 failures
gcc 2.95.3, binutils HEAD All 616 tests passed
gcc 3.2.1, binutils HEAD All 648 tests passed
gcc gcc-3_2-branch, binutils 2.13.2.1 All 648 tests passed
gcc gcc-3_2-branch, binutils HEAD All 648 tests passed
gcc gcc-3_2-branch, binutils vendor All 648 tests passed
gcc gcc-3_3-branch, binutils 2.13.2.1 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.13.2.1 649 tests, 0 failures
gcc HEAD, binutils HEAD 649 tests, 0 failures
gcc HEAD, binutils vendor 649 tests, 0 failures
gdb gdb_5_3-branch All 649 tests passed
gdb HEAD 649 tests, 0 failures
. Gdb Testing
My tables are at:
http://www.shout.net/~mec/sunday/2003-01-20/index.html
The previous report was 2003-01-15:
http://www.shout.net/~mec/sunday/2003-01-15/Analysis.txt
. Counts
gdb 5.3: 0 build aborts, 0 test aborts, 384 non-PASS results
gdb gdb_5_3_branch: 0 build aborts, 0 test aborts, 388 non-PASS results
gdb HEAD: 0 build aborts, 0 test aborts, 342 non-PASS results
A non-PASS result is any result except PASS. This includes ERROR,
WARNING, NOTE, FAIL, KPASS, KFAIL, XPASS, XFAIL, UNRESOLVED,
UNTESTED, UNSUPPORTED, and unknown results.
. 5.3
. gdb.c++/annota2.exp: annotate-quit
pr gdb/544: gdb.c++/annota2.exp: annotate-quit test sometimes fails
http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=544
Fluctuation in test result from unknown cause.
. gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
pr gdb/568: GDB confused by messily-exiting multi-threaded programs
http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=568
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_5_3-branch
cvs checkout start 2003-01-20T15:29:34Z
cvs checkout finish 2003-01-20T15:31:08Z
The cvs checkout time was 197 seconds in the last report
(T03:56:38Z to T03:59:55Z) and is 94 seconds in this report.
. gdb.c++/annota2.exp: annotate-quit
gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
gdb.threads/schedlock.exp: *
Same analysis as 5.3.
. HEAD
cvs checkout start 2003-01-20T15:27:59Z
cvs checkout finish 2003-01-20T15:29:34Z
The cvs checkout time was 141 seconds in the last report
(T03:54:17Z to T03:56:38Z) and is 95 seconds in this report.
. gdb.c++/annota2.exp: annotate-quit
gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
Same analysis as 5.3
. gdb.c++/cplusfuncs.exp: print &'hairyfunc5'
gdb.c++/cplusfuncs.exp: print &'hairyfunc6'
gdb.c++/cplusfuncs.exp: print &'hairyfunc7'
FAIL -> KFAIL
David C enabled KFAIL for a known bug.
. gdb.c++/demangle.exp: lucid: __vtbl__3foo__vt_cc_main_
XFAIL -> KFAIL
David C enabled KFAIL for a known bug.
. gdb.c++/inherit.exp: print g_D.A::a
gdb.c++/inherit.exp: print g_D.A::x
gdb.c++/inherit.exp: print g_E.A::a
gdb.c++/inherit.exp: print g_E.A::x
XFAIL -> KFAIL
David C enabled KFAIL for a known bug.
. gdb.threads/schedlock.exp: *
These results are as flaky as New England snow storm.
This test is still in a state where it's better to analyze the
absolute results than to compare results from date to date.
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
gdb => 5.3, gdb_5_3-branch%20030120, HEAD%20030120
gcc => 2.95.3, 3.2-7-rh, 3.2.1, gcc-3_2-branch%20030119, gcc-3_3-branch%20030119, HEAD%20030119
binutils => 2.13.90.0.2-rh, 2.13.2.1, HEAD%200230119
libc => 2.2.93-5-rh
gformat => dwarf-2, stabs+
count 96 = 1 * 1 * 1 * 3 * (5+3*1+1) * 1 *2
Note that gcc/binutils were checked out and built one day before gdb was
checked out and built.
'target' and 'host' are gnu configuration triples.
'osversion' is the host operating system name, which is additional
information beyond 'host'.
'gdb', 'gcc', 'binutils', and 'libc' 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.
'count' is the total number of configurations tested.
The vendor gcc is available only with vendor binutils,
thus the '(5*3+1*1)' term for gcc/binutils combinations.
. Baseline Software
. host=i686-pclinux-gnu, osversion=red-hat-8.0
make 3.79.1
binutils 2.13.2.1
gcc 3.2.1
flex 2.5.4
bison 1.35
tcl 8.4.1
expect 5.38.0
dejagnu 1.4.3
The baseline software is used to build and test all the other
software. It is not part of the test matrix.
The sources.redhat.com cvs repository has its own versions of tcl,
expect, and dejagnu. The sources.redhat.com versions behave
differently than than the stock versions, especially in the area of
regular expression quoting. I don't have the resources to test with
both tcl/expect/dejagnu stacks, so I choose the stock stack for my
test bed.
I have packaged and published my scripts to manage the baseline
software. They are called Migchain (Michael's Gnu Toolchain),
and they are licensed under the GPL.
ftp://ftp.shout.net/pub/users/mec/migchain/migchain-0.3.tar.gz
. Test Bed Changes Since Last Report
None.