This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2002-12-12
- From: Michael Elizabeth Chastain <mec at shout dot net>
- To: gdb-testers at sources dot redhat dot com
- Date: Mon, 16 Dec 2002 09:32:59 -0600
- Subject: sunday project, gdb, 2002-12-12
Highlights of this report:
. No regressions detected in any version of gdb.
. I added gdb 5.3.
My tables are here:
http://www.shout.net/~mec/sunday/2002-12-12/index.html
Michael C
. Summary
. Test Matrix
. Matrix
target => native
host => i686-pc-linux-gnu%rh-8
gdb => 5.2.1, 5.2.91, 5.3, gdb_5_3-branch%20021212, HEAD%20021212
gcc => 2.95.3, 3.0.4, 3.1, 3.1.1, 3.2, 3.2.1, 3.2-7-rh, gcc-3_2-branch%20021212, HEAD%20021212
binutils => 2.13.90.0.2-rh, 2.13.1, binutils-2_13-branch%20021212, HEAD%20021212
glibc => 2.2.93-5-rh
gformat => dwarf-2, stabs+
count 330 = 1 * 1 * 5 * (8*4+1) * 1 * 2
. Notes
target and host names are gnu triples with extra information after
a '%' delimiter.
versions which start with a number are official releases or snapshots.
versions which start with a number and end with "-rh" are the
vendor-supplied versions on my red hat linux host.
versions named "HEAD" are the cvs HEAD.
versions with any other name are cvs branches.
cvs versions show the checkout date after a '%' delimiter.
. libiberty
Not tested yet (I need to update my test script).
. gdb
. Tables
. http://www.shout.net/~mec/sunday/2002-12-12/index.html
. Overview
gdb 5.2.1: 0 build aborts, 0 test aborts, 514 attention lines
gdb 5.2.91: 0 build aborts, 0 test aborts, 392 attention lines
gdb 5.3: 0 build aborts, 0 test aborts, 395 attention lines
gdb gdb_5_3-branch: 0 build aborts, 0 test aborts, 400 attention lines
gdb HEAD: 0 build aborts, 0 test aborts, 426 attention lines
An attention line is a test with an attention results in one or
more configurations.
An attention result is any result except PASS. This includes
ERROR, WARNING, FAIL, KPASS, KFAIL, XPASS, XFAIL, UNRESOLVED,
UNTESTED, UNSUPPORTED, and unknown results.
. Old bugs fixed
No old bug fixes were detected in gdb.
. New bugs detected
No new bugs were detected in gdb.
. Test protocol changes since last report
I added gdb 5.3.
I upgraded my baseline compiler from gcc 2.95.3 to gcc 3.2.1 in an
attempt to fix a problem with readline 4.3 in gdb HEAD. This was
not entirely successful: the problem disappeared, then re-appeared,
and I had to find another workaround. Now I change $LANG from its
default value of "en_US.UTF-8" to "en_US", which avoids a problem in
the readline multibyte code.
Now that gdb 5.3 is in, I am planning to drop gdb 5.2.1 and gdb 5.2.91
in the next report.
I dropped the "compare by date: all dates" tables for this report and
may drop them permanently. I am not using them at this time and I
don't know anyone who is.
. Baseline software
. host i686-pc-linux-gnu%rh-8
make 3.79.1
binutils 2.13.1
gcc 3.2.1
flex 2.5.4
bison 1.35
tcl 8.3.4
expect 5.33.0
dejagnu 1.4.2 + FernandoN kfail patch.
The baseline software is used to build all the other software.
It is not part of the test matrix.
I will be upgrading the baseline software as time becomes available,
starting with dejagnu 1.4.3, which has KFAIL support integrated.
. Analysis
. libiberty
. results
. target native
. host i686-pc-linux-gnu%rh-8
No results available yet.
. gdb
The last report was 2002-12-03:
http://www.shout.net/~mec/sunday/2002-12-03/Analysis.txt
. 5.2.1
. gdb.base/selftest.exp: unknown source line near main
gdb.base/selftest.exp: step into xmalloc call
(blank) -> FAIL, PASS -> FAIL
selftest.exp operates on the gdb binary, so this test is sensitive
to the baseline C compiler version. I upgraded the baseline C
compiler which revealed a deficiency in the test script.
David Carlton analyzes this problem and submits a patch for
gdb HEAD in:
http://sources.redhat.com/ml/gdb-patches/2002-12/msg00369.html
. gdb.c++/annota2.exp
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.
. 5.2.91
. gdb.base/selftest.exp: unknown source line near main
gdb.base/selftest.exp: step into xmalloc call
(blank) -> FAIL, PASS -> FAIL
selftest.exp operates on the gdb binary, so this test is sensitive
to the baseline C compiler version. I upgraded the baseline C
compiler which revealed a deficiency in the test script.
David Carlton analyzes this problem and submits a patch for
gdb HEAD in:
http://sources.redhat.com/ml/gdb-patches/2002-12/msg00369.html
. 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 Blandy 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 Jacobowitz has an obvious fix, which has been applied
to gdb HEAD:
http://sources.redhat.com/ml/gdb-patches/2002-10/msg00454.html
. gdb.trace/actions.exp: ERROR: couldn't load /berman/fsf/_today_berman/test/gdb.trace/actions into gdb (timeout out)
This ERROR mysteriously appeared on 2002-12-03, and mysteriously
disappeared on 2002-12-12. actions.exp is fine right now.
I am leaving this in the "unexplained mystery" pile.
. 5.3
This is the first full report for 5.3.
I have limited results from a small test run on 2002-12-11 which I
ran on the 5.2.92 tarball. There are no test result changes from
2002-12-11 to 2002-12-12 which indicate significant changes in gdb.
. gdb_5_3-branch
. gdb.base/selftest.exp: unknown source line near main
gdb.base/selftest.exp: step into xmalloc call
(blank) -> FAIL, PASS -> FAIL
selftest.exp operates on the gdb binary, so this test is sensitive
to the baseline C compiler version. I upgraded the baseline C
compiler which revealed a deficiency in the test script.
David Carlton analyzes this problem and submits a patch for
gdb HEAD in:
http://sources.redhat.com/ml/gdb-patches/2002-12/msg00369.html
. 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 Blandy 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 branch because of a
signed-versus-unsigned bug.
Daniel Jacobowitz has an obvious fix, which has been applied
to gdb HEAD:
http://sources.redhat.com/ml/gdb-patches/2002-10/msg00454.html
. gdb.trace/actions.exp: ERROR: couldn't load /berman/fsf/_today_berman/test/gdb.trace/actions into gdb (timeout out)
This ERROR popped up on 2002-12-12 with gcc=3.0.4,
binutils=binutils-2_13-branch%2002-12-12, gformat=stabs+.
I am adding this to the "unexplained mystery" pile.
. HEAD
. gdb.base/selftest.exp: backtrace through signal handler
FAIL -> PASS
pr gdb/862: regression: gdb.base/selftest.exp: "backtrace through signal handler"
http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=862
Daniel Jacobowitz fixed a bug in the test script.
. gdb.base/selftest.exp: unknown source line near main
gdb.base/selftest.exp: step into xmalloc call
(blank) -> FAIL, PASS -> FAIL
selftest.exp operates on the gdb binary, so this test is sensitive
to the baseline C compiler version. I upgraded the baseline C
compiler which revealed a deficiency in the test script.
David Carlton analyzes this problem and submits a patch for
gdb HEAD in:
http://sources.redhat.com/ml/gdb-patches/2002-12/msg00369.html
. gdb.base/store.exp: Process no longer exists
(blank) -> ERROR [12 times]
gdb.base/store.exp: new check struct 1
gdb.base/store.exp: new up struct 1
gdb.base/store.exp: old check struct 1
gdb.base/store.exp: old up struct 1
(blank) -> FAIL
gdb.base/store.exp: new check struct 2
gdb.base/store.exp: new check struct 3
gdb.base/store.exp: new check struct 4
gdb.base/store.exp: new up struct 2
gdb.base/store.exp: new up struct 3
gdb.base/store.exp: new up struct 4
gdb.base/store.exp: old check struct 2
gdb.base/store.exp: old check struct 3
gdb.base/store.exp: old check struct 4
gdb.base/store.exp: old up struct 2
gdb.base/store.exp: old up struct 3
gdb.base/store.exp: old up struct 4
(blank) -> UNRESOLVED
store.exp is a new test script. Some of its calls to
"check_struct" and "up_struct" contain unquoted brace
characters, which causes problems with my versions of
tcl/expect/dejagnu. I am using tcl 8.3.4, expect 5.33.0,
and dejagnu 1.4.2 + FernandoN kfail patch.
I am going to leave these ERRORs hanging while I work
on upgrading my test bed to tcl 8.4.1, expect 5.38.0, and
dejagnu 1.4.3.
. gdb.base/store.exp: continue field 1
gdb.base/store.exp: next field 1
gdb.base/store.exp: continue field 2
gdb.base/store.exp: next field 2
gdb.base/store.exp: continue field 3
gdb.base/store.exp: next field 3
gdb.base/store.exp: continue field 4
gdb.base/store.exp: next field 4
(blank) -> FAIL
store.exp is a new test script. These tests break on a
function, "continue" to the function, and then check the
source line. It looks like the prologue scanner is off by one.
This happens with gcc = 3.0.4, binutils = *, gformat = *.
It does not happen with gcc 2.95.3, gcc 3.1, gcc 3.1.1, gcc 3.2,
gcc 3.2.1, gcc gcc-3_2-branch%20021212, or gcc HEAD%20021212.
I do not consider gcc 3.0.4 a supported configuration any more,
so these FAILs are not important to me.
. 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.c++/m-data.exp: shadowed global variable
(blank) -> PASS
This new test PASSed in all configurations.
gdb.c++/m-data.exp: shadowing member
(blank) -> PASS
(blank) -> FAIL
This new test PASSEd in all configurations with gcc 2.95.3, gcc
3.1, gcc 3.1.1, gcc 3.2, gcc 3.2.1, gcc gcc-3_2-branch%20021212,
and gcc HEAD%20021212.
This test FAILed in all configurations with gcc 3.0.4. I do
not consider gcc 3.0.4 a supported configuration any more,
so this FAIL is not important to me.
. gdb.mi/gdb669.exp: console and MI have same number of threads
gdb.mi/gdb669.exp: -thread_list_ids
gdb.mi/gdb669.exp: MI and console have same threads
gdb.mi/gdb669.exp: finding threads in MI output
Some configurations improved, and some configurations
disimproved. Looks like multi-threading still has issues.
. 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 Blandy 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: *
Both good and bad changes. This test is still in a state
where it's better to analyze the absolute results than to
compare results from date to date.