This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-04-02
- 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: Thu, 3 Apr 2003 12:16:22 -0600
- Subject: sunday project, gdb, 2003-04-02
My tables are here:
http://www.shout.net/~mec/sunday/2003-04-02/index.html
Michael C
. Old Bugs Fixed
None.
. New Bugs Detected
. gdb HEAD
. gdb.base/relocate.exp: *
gdb stops responding to input and the test suite times out.
This happened with gcc v2 and gcc v3, -gstabs+.
This did not happen with gcc v2 and gcc v3, -gdwarf-2.
. gdb.mi/mi-cli.exp: -interpreter-exec-console "set $pc=0x0"
This test causes an internal error:
/berman/fsf/_today_/source/gdb/HEAD/src/gdb/frame.c:63:
internal-error:
get_frame_id: Assertion `!legacy_frame_p (current_gdbarch)' failed.
This happened in all configurations tested.
. PR Count
Query executed 2003-04-03T15:53:27Z
1171 matches found
19 analyzed
488 closed
17 feedback
634 open
4 paperwork
9 suspended
1171 TOTAL
. 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_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-04-02/index.html
The previous report was 2003-03-25:
http://www.shout.net/~mec/sunday/2003-03-25/Analysis.txt
. Non-PASS Results
gdb 5.3: 0 test aborts, 384 non-PASS results
gdb HEAD: 0 test aborts, 390 non-PASS 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
. HEAD
checkout date is '2003-04-02 21:50:51 UTC'
. gdb.base/gdb1090.exp: up from marker
null -> PASS
gdb.base/gdb1090.exp: print s24
null -> KFAIL
Michael C wrote a new test script.
. gdb.base/ptype.exp: ptype func_type
FAIL -> PASS
gdb.base/ptype.exp: ptype t_char_array
FALL -> PASS
Michael C fixed a bug in the test program.
. gdb.base/relocate.exp: *
PASS -> FAIL
PASS -> null
null -> FAIL
gdb goes into the weeds and many tests time out.
This happened with gcc 2.95.3 -gstabs+ and gcc v3 -gstabs+.
It did not happen with gcc 2.95.3 -gdwarf-2 and gcc v3 -gdwarf-2.
# gdb.log excerpt
(gdb) add-symbol-file /berman/fsf/_today_/berman/test/gdb.base/relocate.o 0
add symbol table from file "/berman/fsf/_today_/berman/test/gdb.base/relocate.o" at
.text_addr = 0x0
(y or n) y
Reading symbols from /berman/fsf/_today_/berman/test/gdb.base/relocate.o...done.
(gdb) PASS: gdb.base/relocate.exp: add-symbol-file relocate.o 0
print &static_foo
FAIL: gdb.base/relocate.exp: get address of static_bar (timeout)
FAIL: gdb.base/relocate.exp: static variables have different addresses
FAIL: gdb.base/relocate.exp: get address of global_foo (timeout)
FAIL: gdb.base/relocate.exp: get address of global_bar (timeout)
FAIL: gdb.base/relocate.exp: global variables have different addresses
FAIL: gdb.base/relocate.exp: get address of function_foo (timeout)
FAIL: gdb.base/relocate.exp: get address of function_bar (timeout)
FAIL: gdb.base/relocate.exp: functions have different addresses
testcase /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/relocate.exp completed in 0 seconds
. gdb.base/sizeof.exp: check valueof '\\377' == -1
gdb.base/sizeof.exp: get value of '\377' (-1)
null -> PASS
Andrew C wrote new tests.
. gdb.c++/annota2.exp: annotate-quit
Same analysis as 5.3.
. gdb.c++/casts.exp: run
FAIL -> null
gdb.c++/casts.exp: continue
null -> FAIL
The test suite changed the way that it invokes programs, which
caused a difference in results. This happened with gcc HEAD
-gstabs+, which is a broken configuration (pr gcc/10055).
This difference is not important.
. gdb.gdb/observer.exp: *
null -> PASS
Joel B wrote a new test script.
All tests PASSed in all configurations tested.
. gdb.mi/mi-cli.exp: Process no longer exists
null -> ERROR
gdb.mi/mi-cli.exp: -interpreter-exec-console "set $pc=0x0"
PASS -> UNRESOLVED
This is a regression in gdb.
This happened in all configurations tested.
# gdb.log excerpt
(gdb) ^M
PASS: gdb.mi/mi-cli.exp: -interpreter-exec console "help set args"
888-interpreter-exec console "set $pc=0x0"^M
&"/berman/fsf/_today_/source/gdb/HEAD/src/gdb/frame.c:63: internal-error: get_frame_id: Assertion `!legacy_frame_p (current_gdbarch)' failed.\n"^M
&"A problem internal to GDB has been detected. Further\ndebugging may prove unreliable.\n"^M
ERROR: Process no longer exists
UNRESOLVED: gdb.mi/mi-cli.exp: -interpreter-exec console "set $pc=0x0"
testcase /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.mi/mi-cli.exp completed in 1 seconds
. gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
Same analysis as 5.3.
. gdb.threads/schedlock.exp: *
New date, same story.
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%20030402
gcc => 2.95.3, 3.2-7-rh, 3.2.2, gcc-3_2-branch%20030401, gcc-3_3-branch%20030401, HEAD%20030401
binutils => 2.13.90.0.2-rh, 2.13.2.1, HEAD%20030401
glibc => 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count 64 = 1 * 1 * 1 * 2 * (5*3+1*1) * 1 * 2 * 1
'target' and 'host' are gnu configuration triples.
'osversion' is the host operating system name, which is additional
information beyond 'host'.
'gdb', 'gcc', 'binutils', and 'glibc' 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.
'glevel' is the debugging level.
'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-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
None.