This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-08-28
- 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: Fri, 29 Aug 2003 13:13:03 -0400
- Subject: sunday project, gdb, 2003-08-28
. Highlights of this report
Daniel J fixed pr gdb/1322, a nasty Java bug.
Michael C
. Old Bugs Fixed
. gdb HEAD
http://sources.redhat.com/gdb/bugs/1322
"internal-error: sect_index_text not initialized" after printing a java type
Daniel J fixed this in gdb HEAD.
. New Bugs Detected
None.
. PR Count
Query executed 2003-08-29T17:05:53Z
1361 matches found
22 analyzed
610 closed
29 feedback
686 open
3 paperwork
11 suspended
1361 TOTAL
. Libiberty Testing
. target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
binutils HEAD 714 tests, 31 failures
gcc 2.95.3, binutils HEAD All 616 tests passed
gcc 3.3.1, binutils HEAD 649 tests, 0 failures
gcc gcc-3_3-branch, binutils 2.14 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 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-08-28/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2003-08-23/index.html
. Non-PASS Results
gdb 5.3 417 non-PASS results
gdb gdb_6_0-branch 406 non-PASS results
gdb HEAD 447 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/print-threads.exp: Hit kill breakpoint, 10 (slow with kill breakpoint)
PASS -> blank
Fluctuation with unknown cause. Probably harmless.
. 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-08-28 16:20:10 UTC'
previous date is '2003-08-24 00:22:36 UTC'
. gdb.c++/annota2.exp: annotate-quit
gdb.c++/annota3.exp: annotate-quit
Same analysis as gdb 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
gdb.mi/mi2-pthreads.exp: check mi_thread_command_set: -thread-select 3
gdb.mi/mi2-pthreads.exp: check mi_thread_command_set: -thread-select 4
gdb.mi/mi2-pthreads.exp: check mi_thread_command_set: -thread-select 5
gdb.mi/mi2-pthreads.exp: check mi_thread_command_set: -thread-select 6
blank -> PASS
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 2 24
thread 1 24 2
thread 2 25 1
thread 3 26 0
thread 4 26 0
thread 5 26 0
. gdb HEAD
checkout date is '2003-08-28 16:15:29 UTC'
previous date is '2003-08-24 00:19:35 UTC'
. gdb.c++/annota2.exp: annotate-quit
gdb.c++/annota3.exp: annotate-quit
Same analysis as gdb 5.3.
. gdb.java/jmisc.exp: *
gdb.java/jmisc1.exp: *
gdb.java/jmisc2.exp: *
Java compilation timeout from last report did not happen this time.
This is a deficiency in my test bed.
. gdb.java/jmisc1.exp: continue to exit
KFAIL -> PASS
Daniel J fixed pr gdb/1322.
http://sources.redhat.com/gdb/bugs/1322
"internal-error: sect_index_text not initialized" after printing a java type
. 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.mi1/mi-pthreads.exp: check mi_thread_command_set: -thread-select 3
gdb.mi1/mi-pthreads.exp: check mi_thread_command_set: -thread-select 4
gdb.mi1/mi-pthreads.exp: check mi_thread_command_set: -thread-select 5
gdb.mi1/mi-pthreads.exp: check mi_thread_command_set: -thread-select 6
gdb.mi2/mi-pthreads.exp: check mi_thread_command_set: -thread-select 3
gdb.mi2/mi-pthreads.exp: check mi_thread_command_set: -thread-select 4
gdb.mi2/mi-pthreads.exp: check mi_thread_command_set: -thread-select 5
gdb.mi2/mi-pthreads.exp: check mi_thread_command_set: -thread-select 6
PASS -> blank
blank -> PASS
Same analysis as gdb gdb_6_0-branch.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 10 (slow with kill breakpoint)
blank -> PASS
Same analysis as gdb 5.3.
. gdb.threads/schedlock.exp: *
PASS
FAIL
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 almost all configurations except for the
"thread N ran" tests. Here are the counts per thread.
PASS FAIL
thread 0 3 23
thread 1 22 4
thread 2 25 1
thread 3 26 0
thread 4 24 2
thread 5 26 0
One configuration had anomalous results with many FAILs:
# gdb.log excerpt
# target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0
# gdb=HEAD 2003-08-28 16:15:29 UTC
# gcc=HEAD 2003-08-27 18:36:47 UTC
# binutils=2.14
# gformat=dwarf-2, glevel=2
(gdb) break 41 if arg != 5
Breakpoint 3 at 0x80484d1: file /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.threads/schedlock.c, line 41.
(gdb) continue
Continuing.
Program received signal SIGINT, Interrupt.
[Switching to Thread 24580 (LWP 9479)]
0x42028c82 in sigprocmask () from /lib/i686/libc.so.6
(gdb) FAIL: gdb.threads/schedlock.exp: continue to breakpoint: return to loop (initial)
... many more FAILS ...
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
gdb => 5.3, gdb_6_0-branch, HEAD
gcc => 2.95.3, 3.2-7-rh, 3.3.1, gcc-3_3-branch, HEAD
binutils => 2.13.90.0.2-rh, 2.14, HEAD
glibc => 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count 78 = 1 * 1 * 1 * 3 * (4*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.
'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*3+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 Gnu 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
I adjusted the fuzzy names of 'gdb.mi/mi0-*' and 'gdb.mi/mi1-*'
from 'gdb.mi[01]-*' to 'gdb.mi1.mi0-*'. No big deal.
I dropped target binutils binutils-2_14-branch. Daniel J says that
there will not be another binutils release from this branch.