This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-08-10
- 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: Mon, 11 Aug 2003 22:13:33 -0400
- Subject: sunday project, gdb, 2003-08-10
. Highlights of this report
gcc 3.3.1 has no debug regressions compared to gcc 3.3
for native i686-pc-linux-gnu with -gdwarf-2 and -gstabs+.
The new gdb.mi/mi2-*.exp tests are working fine in HEAD and branch.
gdb HEAD 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'
These two PR's are actually the same bug. Michael C and Mark K
fixed the bug on gdb HEAD. Mark K will port the fix to gdb
gdb_6_0-branch soon.
Andrew C fixed the seg fault for "gdb -i=mi2".
. New Bugs Detected
None.
. PR Count
Query executed 2003-08-12T01:35:52Z
1330 matches found
20 analyzed
589 closed
19 feedback
688 open
3 paperwork
11 suspended
1330 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 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-10/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2003-08-07/index.html
. Non-PASS Results
gdb 5.3 368 non-PASS results
gdb gdb_6_0-branch 332 non-PASS results
gdb HEAD 360 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-08-10 17:29:11 UTC'
previous date is '2003-08-07 20:31:55 UTC'
. gdb.base/annota3.exp: annotate ignore count change (pattern 5)
FAIL -> PASS
PASS -> FAIL
This test FAILed in 2 configurations out of 42 tested.
I have not analyzed this yet.
. 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
blank -> PASS
PASS -> blank
Fluctuation with unknown cause. Probably harmless.
. gdb.mi/mi2-*.exp: *
PASS
FAIL
KFAIL
XFAIL
Andrew C fixed a bug in gdb, so these tests do more now than
just crash gdb (although that is a valuable test!)
These tests are forked from gdb.mi/mi-*.exp. Counted over all
configurations, I have 586 results with 29 non-PASS results.
All of the non-PASS results are copies of similar results for
gdb.mi/mi-*.exp.
. gdb.objc/basicclass.exp: successfully compiled objc with posix threads test case
UNRESOLVED -> PASS
This was a cascade error from tcl errors in the previous file,
gdb.mi2/mi2-watch.exp.
. 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 6 36
thread 1 28 14
thread 2 39 3
thread 3 41 1
thread 4 39 3
thread 5 42 0
. gdb HEAD
checkout date is '2003-08-10 17:25:06 UTC'
previous date is '2003-08-07 20:28:13 UTC'
. gdb.arch/i386-prologue.exp: backtrace in gdb1253
gdb.arch/i386-prologue.exp: continue to gdb1253
blank -> PASS
Mark K wrote a new test script. All tests PASSed in all
configurations.
. gdb.base/annota3.exp: annotate ignore count change (pattern 5)
FAIL -> PASS
PASS -> FAIL
The 'annotate ignore count change' test FAILed in 8
configurations out of 42 tested.
I have not analyzed this yet.
. gdb.c++/annota2.exp: annotate-quit
Same analysis as gdb 5.3.
. gdb.mi/mi-syn-frame.exp: 407-stack-list-frames
FAIL -> PASS
Michael C and Mark K fixed a bug in gdb.
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.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
Same analysis as gdb gdb_6_0-branch.
. gdb.mi/mi2-*.exp: *
PASS
FAIL
KFAIL
XFAIL
Same analysis as gdb gdb_6_0-branch.
Counted over all configurations, I have 587 results with 28
non-PASS results. All of the non-PASS results are copies of
similar results for gdb.mi/mi-*.exp.
. gdb.objc/basicclass.exp: successfully compiled objc with posix threads test case
UNRESOLVED -> PASS
Same analysis as gdb gdb_6_0-branch.
. gdb.threads/linux-dp.exp: main is distinct: 1
blank -> PASS
. gdb.threads/linux-dp.exp: philosopher is distinct: 1
PASS -> blank
This is another manifestation of the bug fix for 'backtrace in
sleep'. The test is written so that it PASSes with 'main is
distinct' for a good backtrace, and it PASSes with 'philosopher
is distinct' for a slightly bad backtrace!
I must have missed an earlier transition from PASS to blank.
http://sources.redhat.com/gdb/bugs/1255
[regression] bad backtrace for libc function 'sleep'
. 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
gdb.threads/pthreads.exp: check backtrace from main thread
gdb.threads/pthreads.exp: check backtrace from thread 2
gdb.threads/pthreads.exp: apply backtrace command to all three threads
FAIL -> PASS
Bug fix for 'backtrace in sleep'.
http://sources.redhat.com/gdb/bugs/1255
[regression] bad backtrace for libc function 'sleep'
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (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 2 40
thread 1 39 3
thread 2 41 1
thread 3 41 1
thread 4 42 1
thread 5 40 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, 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 * (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.
'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.
. 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 added target gcc 3.3.1.
Next report, I will drop target gcc 3.3.