This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-02-01
- From: Michael Elizabeth Chastain <mec at shout dot net>
- To: gdb-testers at sources dot redhat dot com
- Date: Sun, 2 Feb 2003 01:03:41 -0600
- Subject: sunday project, gdb, 2003-02-01
Highlights of this report:
. gdb PR count: 576 open, 16 analyzed, 8 suspended, 15 feedback,
0 paperwork, 401 closed. Query executed 2003-02-01T20:47:55Z.
. gdb_5_3-branch has had no activity since the last report on 2003-01-20.
. No new bugs detected.
My tables are here:
http://www.shout.net/~mec/sunday/2003-02-01/index.html
Michael C
. Old Bugs Fixed
Someone fixed a bug in gdb which led to improved results
in gdb.base/store.exp.
. 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-02-01/index.html
The previous report was 2003-01-20:
http://www.shout.net/~mec/sunday/2003-01-20/Analysis.txt
. Counts
gdb 5.3: 0 build aborts, 0 test aborts, 378 non-PASS results
gdb gdb_5_3_branch: 0 build aborts, 0 test aborts, 385 non-PASS results
gdb HEAD: 0 build aborts, 0 test aborts, 339 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-02-01T17:35:53Z
cvs checkout finish 2003-02-01T17:37:42Z
. 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-02-01T17:34:06Z
cvs checkout finish 2003-02-01T17:35:53Z
. gdb.base/store.exp: new up struct 1
gdb.base/store.exp: new up struct 2
FAIL->PASS
Someone fixed a bug in gdb.
. gdb.c++/annota2.exp: annotate-quit
gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
Same analysis as 5.3
. gdb.threads/schedlock.exp: *
These results are as confused as a gaijin in Shinjuku Station.
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%20030201, HEAD%20030201
gcc => 2.95.3, 3.2-7-rh, 3.2.1, gcc-3_2-branch%20030128, gcc-3_3-branch%20030128, HEAD%20030128
binutils => 2.13.90.0.2-rh, 2.13.2.1, HEAD%20030131
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 is several days older than gdb. gcc gcc-3_3-branch and
gcc HEAD have a build breakage with 'make install' in the libffi
directory. I reported the problem (so did several other people)
and backed off to the date just before libffi broke.
http://gcc.gnu.org/ml/gcc-bugs/2003-01/msg01822.html
My binutils is one day older than my gdb.
'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 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 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
I installed a new hard disk in my primary host, so I re-built the
test bed from scratch. I wasn't able to do before-and-after testing
of this change, but the test bed is operating fine now.