This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-08-16
- 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: Sun, 17 Aug 2003 16:52:37 -0400
- Subject: sunday project, gdb, 2003-08-16
. Highlights of this report
gdb gdb_6_0-branch improved on the backtrace bugs.
Michael C
. Old Bugs Fixed
http://sources.redhat.com/gdb/bugs/1253
[regression] bad backtrace for '<function called from gdb>'
http://sources.redhat.com/gdb/bugs/1255
[regression] bad backtrace for libc function 'sleep'
Mark K ported a bug fix from gdb HEAD to gdb gdb_6_0-branch.
. New Bugs Detected
http://sources.redhat.com/gdb/bugs/1322
"internal-error: sect_index_text not initialized" after printing a java type
A new test found an existing bug in gdb.
http://sources.redhat.com/gdb/bugs/1338
can't backtrace through select()
This is another backtrace bug. gdb 5.3 also has this bug, so this
is not a regression.
. PR Count
Query executed 2003-08-17T20:35:23Z
1338 matches found
19 analyzed
595 closed
26 feedback
684 open
3 paperwork
11 suspended
1338 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.1, binutils binutils-2_14-branch 649 tests, 0 failures
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 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-08-16/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2003-08-10/index.html
. Non-PASS Results
gdb 5.3 350 non-PASS results
gdb gdb_6_0-branch 330 non-PASS results
gdb HEAD 359 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, 9 (slow with kill breakpoint)
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-16 19:52:12 UTC'
previous date is '2003-08-10 17:29:11 UTC'
. gdb.base/annota3.exp: annotate ignore count change (pattern 5)
FAIL -> PASS
This test FAILed in 0 configurations out of 34 tested.
Daniel J analyzed this and found a bug in the test script.
He has committed a patch to both gdb HEAD and gdb_6_0-branch.
. gdb.java/jmisc.exp: Couldn't compile /berman/fsf/_today_/source/gdb/gdb_6_0-branch/src/gdb/testsuite/gdb.java/jmisc.java
blank -> UNTESTED
gdb.java/jmisc.exp: *
* -> *
gdb.java/jmisc1.exp: Couldn't compile /berman/fsf/_today_/source/gdb/gdb_6_0-branch/src/gdb/testsuite/gdb.java/jmisc.java
gdb.java/jmisc1.exp: *
* -> *
One configuration blew up on 2 of the 3 java tests. The
configuration was: gdb gdb_6_0-branch, gcc HEAD, binutils 2.14,
gformat stabs+.
Red Hat Linux 8 has a 4:00 AM cron job. This configuration ran
right into the cron job, and the test run took twice as long
as normal (normal is 15 minutes):
Test Run By mgnu on Sun Aug 17 03:58:32 2003
runtest completed at Sun Aug 17 04:29:47 2003
This configuration worked fine when I re-ran it on a quiet
system.
If this happens more often, then we will need to increase the
timeout for Java compilation.
. 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 3
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.mi/mi-syn-frame.exp: 407-stack-list-frames
gdb.mi/mi2-syn-frame.exp: 407-stack-list-frames
gdb.threads/linux-dp.exp: philosopher is distinct: 6
gdb.threads/linux-dp.exp: philosopher is distinct: 7
gdb.threads/pthreads.exp: check backtrace from main threads
gdb.threads/pthreads.exp: apply backtrace command to all three threads
FAIL -> PASS
gdb.threads/linux-dp.exp: main is distinct: 1
blank -> PASS
gdb.threads/linux-dp.exp: philosopher is distinct: 1
PASS -> blank
Mark K ported a bug fix from gdb HEAD to gdb gdb_6_0-branch.
http://sources.redhat.com/gdb/bugs/1253
[regression] bad backtrace for '<function called from gdb>'
http://sources.redhat.com/gdb/bugs/1255
[regression] bad backtrace for libc function 'sleep'
. 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: 3
gdb.threads/linux-dp.exp: philosopher is distinct: 6
gdb.threads/linux-dp.exp: philosopher is distinct: 7
PASS -> FAIL
gdb cannot backtrace through select().
http://sources.redhat.com/gdb/bugs/1338
can't backtrace through select()
This is also a bug with gdb 5.3, but the test script knows
quietly accommodates the symptoms with gdb 5.3 and returns
PASS. I consider that to be a bug in the test script.
. 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: *
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 24
thread 1 26 8
thread 2 31 3
thread 3 32 2
thread 4 32 2
thread 5 34 0
. gdb HEAD
checkout date is '2003-08-16 19:47:28 UTC'
previous date is '2003-08-10 17:25:06 UTC'
. gdb.base/annota3.exp: annotate ignore count change (pattern 5)
PASS -> FAIL
This test FAILed in 3 configurations out of 34 tested.
Same analysis as gdb gdb_6_0-branch.
. gdb.c++/annota2.exp: annotate-quit
. gdb.c++/annota3.exp: annotate-quit
Same analysis as gdb 5.3.
. gdb.java/jmisc1.exp: break exit
blank -> PASS
gdb.java/jmisc1.exp: continue to exit
blank -> KFAIL
Michael C wrote a new test which reveals an existing bug in gdb.
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.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 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
Same analysis as gdb gdb_6_0-branch.
. gdb.threads/linux-dp.exp: philosopher is distinct: 4
gdb.threads/linux-dp.exp: philosopher is distinct: 6
gdb.threads/linux-dp.exp: philosopher is distinct: 7
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb gdb_6_0-branch.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
gdb.threads/print-threads.exp: Hit thread-function breakpoint, 5 (slow with kill breakpoint)
blank -> PASS
Same analysis as gdb gdb_6_0-branch.
. 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 4 30
thread 1 30 4
thread 2 33 1
thread 3 34 0
thread 4 33 1
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, 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, binutils-2_14-branch, HEAD
glibc => 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count 126 = 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.
'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
I dropped target gcc 3.3.