This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-07-18
- 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: Sat, 19 Jul 2003 14:24:21 -0400
- Subject: sunday project, gdb, 2003-07-18
Highlights of this report
. As of 2003-07-17, gcc-3_3-branch has no debug info regressions versus
gcc 3.3, on native i686-pc-linux-gnu with -gdwarf-2 and -stabs+.
. No regressions or improvements anywhere since last report.
Michael C
. Old Bugs Fixed
None.
. New Bugs Detected
None.
. PR Count
Query executed 2003-07-19T18:19:04Z
1291 matches found
18 analyzed
579 closed
23 feedback
657 open
3 paperwork
11 suspended
1291 TOTAL
. Libiberty Testing
. target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
binutils binutils-2_14-branch 649 tests, 0 failures
binutils HEAD 714 tests, 31 failures
gcc 2.95.3, binutils binutils-2_14-branch All 616 tests passed
gcc 2.95.3, binutils HEAD All 616 tests passed
gcc 3.3, binutils binutils-2_14-branch 649 tests, 0 failures
gcc 3.3, binutils HEAD 649 tests, 0 failures
gcc gcc-3_3-branch, binutils 2.14 649 tests, 0 failures
gcc gcc-3_3-branch, binutils binutils-2_14-branch 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.14 714 tests, 31 failures
gcc HEAD, binutils binutils-2_14-branch 714 tests, 31 failures
gcc HEAD, binutils HEAD 714 tests, 31 failures
gcc HEAD, binutils vendor 714 tests, 31 failures
gdb carlton_dictionary-branch 714 tests, 31 failures
gdb gdb_6_0-branch 649 tests, 0 failures
gdb HEAD 714 tests, 31 failures
These are long-standing demangler bugs.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7986
Problems with demangling (__cxa_demangle())
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11028
The standalone C++ demangler doesn't work on some symbols
A libiberty log is available at
http://gcc.gnu.org/ml/gcc/2003-07/msg00032.html
. Gdb Testing
My tables are at
http://www.shout.net/~mec/sunday/2003-07-18/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2003-07-13/index.html
. Non-PASS Results
gdb 5.3: 0 test aborts, 346 non-PASS results
gdb gdb_6_0-branch: 0 test aborts, 300 non-PASS results
gdb HEAD: 0 test aborts, 302 non-PASS results
. 5.3
. gdb.c++/annota2.exp: annotate-quit
http://sources.redhat.com/gdb/bugs/544
gdb.c++/annota2.exp: annotate-quit test sometimes fails
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
http://sources.redhat.com/gdb/bugs/568
GDB confused by messily-exiting multi-threaded programs
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-07-18 19:59:53 UTC'
previous date is '2003-07-13 22:45:07 UTC'
. gdb.c++/annota2.exp: annotate-quit
Same analysis as 5.3.
. 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 4
gdb.mi/mi1-pthreads.exp: check mi_thread_command_set: -thread-select 5
gdb.mi/mi1-pthreads.exp: check mi_thread_command_set: -thread-select 6
PASS -> blank
blank -> PASS
Fluctuation with unknown cause. Probably harmless.
. gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
Same analysis as gdb 5.3.
. gdb.threads/linux-dp.exp: philosopher is distinct: 6
gdb.threads/linux-dp.exp: philosopher is distinct: 7
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.
http://sources.redhat.com/gdb/bugs/1255
[regression] bad backtrace for libc function 'sleep'
. 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" tests. Here are the counts per thread.
PASS FAIL
thread 0 10 34
thread 1 22 12
thread 2 29 5
thread 3 29 5
thread 4 33 1
thread 5 34 0
. gdb HEAD
checkout date is '2003-07-18 19:56:05 UTC'
previous date is '2003-07-13 22:26:35 UTC'
. gdb.base/gdb1250.exp: backtrace from abort
blank -> PASS
blank -> KFAIL
Michael C wrote a new test script with one new test. The new
test PASSed with gcc 2.95.3 and KFAILed with all gcc v3.
http://sources.redhat.com/gdb/bugs/1250
[regression] bad backtrace when function that calls 'abort' at end
. gdb.c++/annota2.exp: annotate-quit
Same analysis as 5.3.
. 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
blank -> PASS
PASS -> blank
Same analysis as gdb gdb_6_0-branch.
. gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
Same analysis as gdb 5.3.
. gdb.threads/linux-dp.exp: philosopher is distinct: 6
gdb.threads/linux-dp.exp: philosopher is distinct: 7
FAIL -> PASS
Same analysis as gdb gdb_6_0-branch.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
PASS -> blank
Fluctuation with unknown cause. Probably harmless.
. 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" tests. Here are the counts per thread.
PASS FAIL
thread 0 3 31
thread 1 31 3
thread 2 33 1
thread 3 33 1
thread 4 34 0
thread 5 34 0
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
gdb => 5.3, gdb_6_0-branch%20030718, HEAD%20030718
gcc => 2.95.3, 3.2-7-rh, 3.3, gcc-3_3-branch%20030717, HEAD%20030717
binutils => 2.13.90.0.2-rh, 2.14, binutils-2_14-branch%20030717, HEAD%20030717
glibc => 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count 102 = 1 * 1 * 1 * 3 * (4*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 '(4*4+1*1)' term for gcc/binutils combinations.
. Host Software
. host=i686-pc-linux-gnu, osversion=red-hat-8.0
make 3.79.1
binutils 2.14
gcc 3.3
flex 2.5.4
bison 1.875
tcl 8.4.3
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
Migbat (Michael's Build and Test), and they are licensed under the
GPL.
ftp://ftp.shout.net/pub/users/mec/migchain/migchain-0.6.tar.gz
ftp://ftp.shout.net/pub/users/mec/migbat/migbat-0.6.tar.gz
. Test Bed Changes Since Last Report
None.