This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-02-15
- 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: Sat, 15 Feb 2003 09:47:59 -0600
- Subject: sunday project, gdb, 2003-02-15
Highlights of this report:
. ^Z works again (pr gdb/1046) but annotate-quit does not (pr gdb/544).
. I dropped coverage of gcc 3.2.1 and gdb gdb_5_3.branch.
. gcc gcc-3_3-branch and gcc HEAD have many -gstabs+ regressions
compared to gcc 3.2.2. This is pr gdb/1026.
pr gdb/1026: regression in casts.exp from gcc 3.2.1 to gcc gcc-3_3-branch%20030128
http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=1026
My tables are here:
http://www.shout.net/~mec/sunday/2003-02-15/index.html
Michael C
. Old Bugs Fixed
pr gdb/1046: regression: ^Z (suspend) no longer works
http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=1046
Andrew C fixed this.
. New Bugs Detected
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
This is an old bug which was fixed for a few days and then
regressed. It's related to signal handling in the command
interpreter.
. PR count
Query executed 2003-2-15T15:43:17Z
1064 matches found
16 analyzed
427 closed
9 feedback
604 open
8 suspended
. 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.2, binutils HEAD 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 HEAD 649 tests, 0 failures
. Gdb Testing
My tables are at:
http://www.shout.net/~mec/sunday/2003-02-15/index.html
The previous report was 2003-02-09:
http://www.shout.net/~mec/sunday/2003-02-09/Analysis.txt
. Counts
gdb 5.3: 0 test aborts, 388 non-PASS results
gdb HEAD: 0 test aborts, 330 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 probably due to a signal handling
race in the command loop.
. 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
checkout date is '2003-02-15 05:30:24 UTC'
The most recent ChangeLog entry is dated 2003-02-04.
I have dropped coverage of this branch as I think it is unlikely
that we will make another release from it.
. HEAD
checkout date is date='2003-02-15 05:27:59 UTC'
. gdb.base/setshow.exp: set radix 11
gdb.base/setshow.exp: set radix 16
gdb.base/setshow.exp: show radix {16}
FAIL -> PASS
gcc HEAD, binutils HEAD, libc vendor, gformat stabs+
The glitches from 2003-02-09 went away. These were cascade
FAILs from a test that changed the command prompt. I
hypothesize that a defect in the test script regular
expression termination interacted with a timing condition in
the gdb command loop. If the glitch comes back, I will look
for a defect in the test script first.
. gdb.c++/annota2.exp: annotate-quit
PASS -> KFAIL
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
Andrew C fixed the ^Z bug in the new command interpreter,
which caused this test to regress.
. gdb.c++/virtfunc.exp: print pEe->D::vg()
XFAIL -> FAIL
XFAIL -> KFAIL
David C changed some setup_xfail calls to kfail's.
This test FAILed with gcc v2 and KFAILed with gcc v3.
. gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
Same analysis as 5.3.
. gdb.threads/schedlock.exp: *
These results continue their long, strange trip.
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, HEAD%20030215
gcc => 2.95.3, 3.2-7-rh, 3.2.2, gcc-3_3-branch%20030214, HEAD%20030214
binutils => 2.13.90.0.2-rh, 2.13.2.1, HEAD%20030214
libc => 2.2.93-5-rh
gformat => dwarf-2, stabs+
count 52 = 1 * 1 * 1 * 2 * (4*3+1*1) * 1 * 2
'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 '(4*3+1*1)' term for gcc/binutils combinations.
. Baseline software
. host=i686-pc-linux-gnu, osversion=red-hat-8.0
make 3.79.1
binutils 2.13.2.1
gcc 3.2.2
flex 2.5.4
bison 1.875
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 dropped target gcc 3.2.1.
I dropped target gdb gdb_5_3-branch.
I upgraded the baseline from gcc 3.2.1 to gcc 3.2.2.
I upgraded the baseline from bison 1.35 to bison 1.875.
I attempted to upgrade the baseline from make 3.79.1 to make 3.80, but
I discovered that 'build.sh' is broken in make 3.80. It turns out
that this is Gnu Make bug #1536.