This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-01-15
- From: Michael Elizabeth Chastain <mec at shout dot net>
- To: gdb-testers at sources dot redhat dot com
- Date: Thu, 16 Jan 2003 13:09:12 -0600
- Subject: sunday project, gdb, 2003-01-15
Highlights of this report:
. no new gdb bugs
. gdb gdb_5_3-branch is active again.
My tables are here:
http://www.shout.net/~mec/sunday/2003-01-15/index.html
Michael C
. Old Bugs Fixed
. Gdb
Daniel J fixed a bug in gdb for resolving overloaded functions
with 'long' or 'short' args.
pr gdb/872: gdb fails overload resolution with TYPE_CODE_INT Types
http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=872
. Test Suite
Mark K fixed gdb.base/default.exp to match a recent change in
'info float'.
Daniel J improved gdb.c++/printmethod.exp to accept '(void)'.
. New Bugs Detected
. Gdb
No new bugs detected.
. Test Suite
http://sources.redhat.com/ml/gdb-patches/2003-01/msg00621.html
The new test scripts gdb.base/advance.exp and gdb.base/until.exp have
bugs which manifest with gcc v3.
. 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-15/index.html
The previous report was 2003-01-09:
http://www.shout.net/~mec/sunday/2003-01-09/Analysis.txt
. Counts
gdb 5.3: 0 build aborts, 0 test aborts, 374 non-PASS results
gdb gdb_5_3_branch: 0 build aborts, 0 test aborts, 375 non-PASS results
gdb HEAD: 0 build aborts, 0 test aborts, 337 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-16T03:56:38Z
cvs checkout finish 2003-01-16T03:59:55Z
I did not cover gdb_5_3-branch in the last report. I checked the
"compare by gdb" tables for differences between gdb 5.3 and gdb
gdb_5_3-branch for the current date. (Actually, I made a subset of
these tables, omitting gdb HEAD, so that I could see the differences
between 5.3 and gdb_5_3-branch more easily).
There were no significant differences between 5.3 and gdb_5_3-branch
for the current date.
. HEAD
cvs checkout start 2003-01-16T03:54:17Z
cvs checkout finish 2003-01-16T03:56:38Z
. gdb.base/advance.exp: *
null -> PASS
gdb.base/advance.exp: advance function not called by current frame
gdb.base/advance.exp: continue to call to func3 in main
gdb.base/advance.exp: advance function called as param
gdb.base/advance.exp: advance with no argument
null -> FAIL
Elena Z wrote a new test script. The indicated tests PASSed with
gcc 2.95.3 and gcc vendor, and FAILed with all gcc 3.*. The
test script needs to accommodate different ways of compiling
C function calls.
http://sources.redhat.com/ml/gdb-patches/2003-01/msg00621.html
After the first FAIL, the test script de-synchronizes with the
program under test and the other FAILs cascade from there.
. gdb.base/args.exp: *
null -> PASS
Elena Z wrote a new test script. All tests PASS.
. gdb.base/constvars.exp: ptype lecherous
gdb.base/constvars.exp: ptype lectern
XPASS -> PASS
Daniel J removed two obsolete setup_xfail's.
. gdb.base/default.exp: info float
FAIL -> PASS
Mark K updated the test script to match a recent change in gdb.
. gdb.base/float.exp: *
null -> PASS
Mark K wrote a new test script. All tests PASS.
. gdb.base/printcmds.exp: ptype &*"foo"
FAIL -> KFAIL
Daniel J enabled KFAIL for a known bug.
. gdb.base/until.exp: *
null -> PASS
gdb.base/until.exp: until func, not called by current frame
null -> FAIL
Elena Z wrote a new test script. The indicated test PASSed with
gcc 2.95.3 and gcc vendor, and FAILed with gcc 3.*. The analysis
is the same as gdb.base/advance.exp.
. gdb.c++/annota2.exp: annotate-quit
Same analysis as 5.3.
. gdb.c++/local.exp: ptype InnerLocal::NestedInnerLocal
FAIL -> KFAIL
Daniel J enabled KFAIL for a known bug.
. gdb.c++/overload.exp: print call overloaded func long arg
gdb.c++/overload.exp: print call overloaded func short arg
gdb.c++/overload.exp: print call overloaded func unsigned long arg
gdb.c++/overload.exp: print call overloaded func unsigned short arg
XFAIL -> PASS
pr gdb/872: gdb fails overload resolution with TYPE_CODE_INT Types
http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=872
Daniel J fixed a bug in gdb for resolving overloaded functions
with 'long' or 'short' args.
. gdb.c++/printmethod.exp: print virtual method.
FAIL -> PASS
Daniel J improved the test script to accept '(void)'.
. gdb.c++/virtfunc.exp: print pBe->vvb()
XPASS -> PASS
Daniel J removed an obsolete setup_xfail.
. gdb.mi/mi-console.exp: Hello message
gdb.mi/mi1-console.exp: Hello message
FAIL -> KFAIL
Daniel J enabled KFAIL for a known bug.
. gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
Same analysis as 5.3.
. gdb.threads/schedlock.exp: *
This test thrashes like Emacs on an IBM PC/XT.
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%20030115, HEAD%20030115
gcc => 2.95.3, 3.2-7-rh, 3.2.1, gcc-3_2-branch%20030114, gcc-3_3-branch%20030114, HEAD%20030114
binutils => 2.13.90.0.2-rh, 2.13.2.1, HEAD%20030114
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
I resumed coverage of gdb_5_3-branch.
I packaged and published the baseline management software. Eventually
I will package and published the test bed software, too.
I changed the order of downloading and building. The old order was:
download gdb, download binutils, download gcc
build gdb, build binutils, build gcc
test gdb
The new order is:
download binutils, build binutils
download gcc, build gcc
download gdb, build gdb
test gdb
This reduces the latency between the beginning of 'download gdb'
and the end of 'test gdb'. It takes me 17 hours for 'build binutils'
and 'build gcc'!
I run 'ntpdate' on my test bed just before downloading, so my reported
cvs checkout times are accurate to 1 second.