This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-09-13
- 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, 14 Sep 2003 19:05:58 -0400
- Subject: sunday project, gdb, 2003-09-13
. Highlights of this report
I'm stepping up my testing frequency because gdb 6.0 is close to
shipping and gcc HEAD has been showing a lot of bugs lately.
No new problems in gcc.
No new problems with gdb gdb_6_0-branch.
One new problem in gdb HEAD with g++ 2.95.3 -gdwarf-2.
Michael C
. Old Bugs Fixed
None.
. New Bugs Detected
http://sources.redhat.com/gdb/bugs/1377
[regression] g++ 2.95.3, dwarf-2, hand function call: SIGSEGV
. PR Count
Query executed 2003-09-14 18:40:32 UTC
1376 matches found
21 analyzed
620 closed
23 feedback
698 open
3 paperwork
11 suspended
1376 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-09-13/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2003-09-11/index.html
. Non-PASS Results
gdb 5.3 418 non-PASS results
gdb 5.3.91 406 non-PASS results
gdb gdb_6_0-branch 400 non-PASS results
gdb HEAD 437 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 5.3.91
. gdb.cp/annota2.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 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
PASS -> blank
blank -> PASS
Fluctuation with unknown cause. Probably harmless.
. gdb.threads/schedlock.exp: *
PASS
gdb.threads/schedlock.exp: thread 0 ran (didn't run)
FAIL
All tests PASSed in all configurations except for the "thread 0
ran" tests, which FAILed in all configurations.
. gdb gdb_6_0-branch
checkout date is '2003-09-13 14:00:00 UTC'
previous date is '2003-09-11 07:19:23 UTC'
. gdb.cp/annota2.exp: annotate-quit
gdb.cp/annota3.exp: annotate-quit
Same analysis as gdb 5.3.
. gdb.java/jmisc.exp: *
WARNING -> blank
UNTESTED -> blank
blank -> PASS
blank -> FAIL
Last report, one configuration had a problem, which was likely to
be a swapping-induced timeout. This report, the problem did not
manifest.
. 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
PASS -> blank
blank -> PASS
Same analysis as gdb 5.3.91.
. gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
Same analysis as gdb 5.3.
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
blank -> PASS
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 4 22
thread 1 22 4
thread 2 26 0
thread 3 25 1
thread 4 25 1
thread 5 26 0
. gdb HEAD
checkout date is '2003-09-13 14:00:00 UTC'
previous date is '2003-09-11 07:16:02 UTC'
. gdb.base/relocate.exp: add-symbol-file relocate.o $offset
gdb.base/relocate.exp: add-symbol-file relocate.o 0
FAIL -> PASS
gdb.stabs/weird.exp: Errors reading weirdx.o
FAIL -> blank
gdb.stabs/weird.exp: weirdx.o read without error
blank -> PASS
Elena Z improved the test scripts to handle new gdb output.
. gdb.cp/annota2.exp: annotate-quit
Same analysis as gdb 5.3.
. gdb.cp/maint.exp: help main cp namespace
gdb.cp/maint.exp: main cp namespace
blank -> PASS
David C added some tests.
. gdb.cp/namespace.exp: ptype C
gdb.cp/namespace.exp: ptype E
blank -> PASS
blank -> FAIL
David C added some tests. "C" and "E" are namespaces,
and these tests just call ptype on them.
With dwarf-2, gdb prints the type of a namespace correctly.
With stabs+, gdb prints "No symbol "C" in current context".
gdb 5.3.91 also prints "No symbol "C" in current context.
So this is a new test for an existing bug, not a regression in gdb.
. gdb.cp/virtfunc.exp: print pBe->vvb()
gdb.cp/virtfunc.exp: print pEe->fvb()
gdb.cp/virtfunc.exp: print pEe->vvb()
PASS -> FAIL
gdb regressed. This happened with gcc 2.95.3 -gdwarf-2.
Here is an excerpt from gdb.log:
# native i686-pc-linux-gnu, red hat 8.0
# gdb HEAD, gcc 2.95.3, binutils 2.14, -gdwarf-2
(gdb) PASS: gdb.cp/virtfunc.exp: print pDd->vg()
print pEe->vvb()^M
^M
Program received signal SIGSEGV, Segmentation fault.^M
0x00000000 in ?? ()^M
The program being debugged was signaled while in a function
called from GDB.^M
GDB remains in the frame where the signal was received.^M
To change this behavior use "set unwindonsignal on"^M
Evaluation of the expression containing the function (at 0x0)
will be abandoned.
^M
(gdb) FAIL: gdb.cp/virtfunc.exp: print pEe->vvb()
I filed a PR:
http://sources.redhat.com/gdb/bugs/1377
[regression] g++ 2.95.3, stabs+, hand function call: SIGSEGV
. 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
PASS -> blank
blank -> PASS
Same analysis as gdb 5.3.91.
. gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
Same analysis as gdb 5.3.
. 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 23
thread 1 25 1
thread 2 24 2
thread 3 24 2
thread 4 24 2
thread 5 26 0
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
gdb => 5.3, 5.3.91, 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 104 = 1 * 1 * 1 * 4 * (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.4
expect 5.39
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
None.