This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-06-25
- 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, 26 Jun 2003 23:58:58 -0400
- Subject: sunday project, gdb, 2003-06-25
Highlights of this report:
. I added gdb gdb_6_0-branch. There are no significant regressions
from gdb HEAD%20030621 to gdb gdb_6_0-branch%20030625.
Michael C
. Old Bugs Fixed
None.
. New Bugs Detected
None.
. PR Count
Query executed 2003-06-27T03:50:11Z
1264 matches found
18 analyzed
574 closed
20 feedback
638 open
3 paperwork
11 suspended
1264 TOTAL
. Libiberty Testing
Not available for this report. I accidentally discarded the log files
before looking at them.
. Gdb Testing
My tables are at:
http://www.shout.net/~mec/sunday/2003-06-25/index.html
The previous report was 2003-06-21:
http://www.shout.net/~mec/sunday/2003-06-21/Analysis.txt
. Non-PASS Results
gdb 5.3: 0 test aborts, 412 non-PASS results
gdb gdb_6_0-branch: 0 test aborts, 432 non-PASS results
gdb HEAD: 0 test aborts, 435 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/gdb/bugs/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/gdb/bugs/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_6_0-branch
checkout date is '2003-06-25 13:03:09 UTC'
This is the first report for this branch. I compared results with
the results from gdb HEAD%20030621 (tables not shown). There were
no significant regressions.
. gdb HEAD
checkout date is '2003-06-25 13:00:35 UTC'
. gdb.base/bang.exp: run program
null -> PASS
Joel B wrote a new test script.
All tests PASSed on all configurations tested.
. gdb.base/langs.exp: print parameter value
gdb.base/langs.exp: set lang to minimal
null -> PASS
Joel B wrote some new tests.
All tests PASSed on all configurations tested.
. gdb.base/relocate.exp: set $offset = 0x10000
gdb.base/relocate.exp: add-symbol-file relocate.o $offset
gdb.base/relocate.exp: get address of function_foo {2}
gdb.base/relocate.exp: function foo has a different address
null -> PASS
Daniel J wrote some new tests.
All tests PASSed on all configurations tested.
. gdb.c++/annota2.exp: annotate-quit
Same analysis as 5.3.
. gdb.c++/pr-1210.exp: step past initialization
null -> PASS
null -> FAIL
gdb.c++/pr-1210.exp: print *obj
gdb.c++/pr-1210.exp: print obj->myB
null -> PASS
Daniel J wrote a new test script. Most tests PASSed in all
configurations. The 'step past initialization' test FAILed with
gcc HEAD -gstabs+ due to an existing bug in gcc HEAD.
pr gcc/10055: [3.4 regression] gcc emits "<internal>" as source filename with -gstabs+
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10055
. gdb.objc/basicclass.exp: *
PASS
Last report, these tests had bad results with the vendor gcc.
They work better after 'rpm -i gcc-objc'! All tests PASSed in
all configurations.
. gdb.threads/linux-dp.exp: philosopher is distinct: 6
gdb.threads/linux-dp.exp: philosopher is distinct: 7
FAIL -> PASS
PASS -> FAIL
These tests are sensitive to a backtrace bug in gdb. If a
thread is waiting on 'select', then gdb prints a deficient
backtrace, and the test FAILs.
pr gdb/1255: [regression] bad backtrace for libc function 'sleep'
http://sources.redhat.com/gdb/bugs/1255
. gdb.threads/pthreads.exp: check backtrace from thread 2
FAIL -> PASS
A multi-threaded inferior program tickles a known bug in
backtracing. The bug is deterministic, but the times when it
happens is not.
pr gdb/1255: [regression] bad backtrace for libc function 'sleep'
http://sources.redhat.com/gdb/bugs/1255
. gdb.threads/schedlock.exp: *
PASS
gdb.threads/schedlock.exp: thread 0 ran (didn't run)
gdb.threads/schedlock.exp: thread 1 ran (didn't run)
gdb.threads/schedlock.exp: thread 2 ran (didn't run)
gdb.threads/schedlock.exp: thread 3 ran (didn't run)
gdb.threads/schedlock.exp: thread 4 ran (didn't run)
gdb.threads/schedlock.exp: thread 5 ran (didn't run)
PASS
FAIL
All tests PASSed in all configurations except for the "thread N
ran" testss. Here are the counts per thread.
PASS FAIL
thread 0 3 39
thread 1 41 1
thread 2 41 1
thread 3 40 2
thread 4 41 1
thread 5 42 0
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
gdb => 5.3, gdb_6_0-branch%20030625, HEAD%20030625
gcc => 2.95.3, 3.2-7-rh, 3.2.3, 3.3, gcc-3_3-branch%20030624, HEAD%20030624
binutils => 2.13.90.0.2-rh, 2.14, binutils-2_14-branch%20030624, HEAD%20030624
glibc => 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count 124 = 1 * 1 * 1 * 3 * (5*4+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*4+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.4.tar.gz
. Test Bed Changes Since Last Report
I installed the vendor objective-c compiler on my host.
Last report there were no regressions from binutils 2.13.2.1 to
binutils 2.14. So I dropped binutils 2.13.2.1 from the target matrix.
Last report there were no regressions from gcc 3.2.2 to gcc 3.2.3. So
I dropped gcc 3.2.2 from the target matrix.