This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-01-09
- From: Michael Elizabeth Chastain <mec at shout dot net>
- To: gdb-testers at sources dot redhat dot com
- Date: Sat, 11 Jan 2003 08:45:28 -0600
- Subject: sunday project, gdb, 2003-01-09
Highlights of this report:
. no new bugs detected (again!)
. gdb gdb_5_3-branch is dormant (still!)
My tables are here:
http://www.shout.net/~mec/sunday/2003-01-09/index.html
Michael C
. Old Bugs Fixed
. Gdb
Daniel J fixed function calls to functions with float arguments.
gdb.base/callfuncs.exp has improved results.
Andrew C, or perhaps Daniel J, improved the MI stack frame information.
gdb.mi/mi-stack.exp and gdb.mi/mi1-stack.exp have improved results.
. Test Suite
Michael C fixed gdb.mi/mi-pthreads.exp and gdb.mi/mi1-pthreads.exp
to work better when libc has no symbols.
. 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 HEAD 649 tests, 0 failures
. Gdb Testing
My tables are at:
http://www.shout.net/~mec/sunday/2003-01-09/index.html
The previous report was 2003-01-04:
http://www.shout.net/~mec/sunday/2003-01-04/Analysis.txt
. Counts
gdb 5.3: 0 build aborts, 0 test aborts, 381 non-PASS results
gdb HEAD: 0 build aborts, 0 test aborts, 345 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
gdb gdb_5_3-branch has been dormant since the relaase.
I will resume test coverage when the branch becomes active.
. HEAD
cvs checkout start 2003-01-09T22:18:14Z
cvs checkout finish 2003-01-09T22:23:43Z
. gdb.base/callfuncs.exp: p t_float_values(3.14159,-2.3765)
gdb.base/callfuncs.exp: p t_float_values(3.14159,float_val2)
gdb.base/callfuncs.exp: p t_float_values(float_val1,-2.3765)
gdb.base/callfuncs.exp: p t_float_values(float_val1,float_val2)
FAIL -> PASS
gdb.base/callfuncs.exp: p t_float_values2(0.0,0.0)
gdb.base/callfuncs.exp: p t_float_values2(3.14159,float_val2)
XPASS -> PASS
Daniel J rewrote the logic in gdb to decide whether a function
is prototyped. This is important when gdb calls a function with
a float argument, because the argument must be coerced to double
if no prototype is in scope (K+R rules) and must be left as
float if a prototype is in scope (Ansi rules).
Daniel J also deleted some setup_xfails's because the tests just
pass now.
. gdb.base/detach.exp: detach, one
gdb.base/detach.exp: detach, two
gdb.base/detach.exp: set should_exit, one
gdb.base/detach.exp: set should_exit, two
null -> PASS
Daniel J wrote a new test.
. gdb.c++/annota2.exp: annotate-quit
Same analysis as 5.3.
. gdb.c++/annota2.exp: watch triggered on a.x
FAIL -> KFAIL
David C changed the test script to refer to PR gdb/38.
. gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 2
gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 7
gdb.mi/mi1-pthreads.exp: check_mi_thread_command_set: -thread-select 2
gdb.mi/mi1-pthreads.exp: check_mi_thread_command_set: -thread-select 7
FAIL -> PASS
gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 3
gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 4
gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 5
gdb.mi/mi-pthreads.exp: check_mi_thread_command_set: -thread-select 6
gdb.mi/mi1-pthreads.exp: check_mi_thread_command_set: -thread-select 6
FAIL -> null
Michael C fixed a bug in the test script. The test script required
gdb to output filename and line number for each selected thread.
But the threads were always (for me) waiting in libc functions,
and some people (like me) test with a stripped libc.
. gdb.mi/mi-stack.exp: stack args listing 0
gdb.mi/mi-stack.exp: stack args listing 1
gdb.mi/mi-stack.exp: stack info-depth
gdb.mi/mi-stack.exp: stack info-depth 99
gdb.mi/mi1-stack.exp: stack args listing 0
gdb.mi/mi1-stack.exp: stack args listing 1
gdb.mi/mi1-stack.exp: stack info-depth
gdb.mi/mi1-stack.exp: stack info-depth 99
FAIL->PASS
Andrew C, or perhaps Daniel J, changed the list of stack frames
by dropping the last frame. I suspect this is a case of
"stopping properly at main" but I'm not sure. I do know that
gdb frame handling changed, the test scripts did not change,
and the test results improved.
. gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
Same analysis as 5.3.
. gdb.threads/schedlock.exp: *
More volatility here than QQQ's on triple witching day.
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%20030109
gcc => 2.95.3, 3.2-7-rh, 3.2.1, gcc-3_2-branch%20030109, gcc-3_3-branch%20030109, HEAD%20030109
binutils => 2.13.90.0.2-rh, 2.13.2.1, HEAD%20030109
libc => 2.2.93-5-rh
gformat => dwarf-2, stabs+
count 64 = 1 * 1 * 1 * 2 * (5*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 '(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.
. Test Bed Changes Since Last Report
None.