This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
sunday project, gdb, 2003-09-26
- 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, 27 Sep 2003 17:08:21 -0400
- Subject: sunday project, gdb, 2003-09-26
. Highlights of this report
gdb gdb_6_0-branch 2003-09-26 10:36:05 UTC is healthy.
The next report, in about 60 hours, will cover gdb 5.3.93.
Michael C
. Old Bugs Fixed
None.
. New Bugs Detected
. gdb HEAD
http://sources.redhat.com/gdb/bugs/826
variables in C++ namespaces have to be enclosed in quotes
http://sources.redhat.com/gdb/bugs/482
gdb.c++/local.exp: ptype InnerLocal::NestedInnerLocal
These bugs re-appeared with gcc v3 -gstabs+.
. PR Count
Query executed 2003-09-27 21:01:22 UTC
1400 matches found
21 analyzed
645 closed
24 feedback
697 open
3 paperwork
10 suspended
1400 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-09-26/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2003-09-22/index.html
. Non-PASS Results
gdb 5.3 344 non-PASS results
gdb 5.3.92 312 non-PASS results
gdb gdb_6_0-branch 315 non-PASS results
gdb HEAD 357 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
. 5.3.92
. gdb.cp/annota2.exp: annotate-quit
gdb.cp/annota3.exp: annotate-quit
Same analysis as gdb 5.3.
. gdb.mi/mi*-pthreads.exp: check mi_thread_command_set: -thread-select [3456]
PASS -> blank
blank -> PASS
When gdb operates on an inferior program with threads, the
thread library in the inferior program behaves differently: it
generates more signals so that gdb can track events.
This causes some programs to behave differently because they
aren't prepared to handle the additional signals. The test
program for mi-pthreads.exp is such a program.
http://sources.redhat.com/ml/gdb/2003-09/msg00279.html
http://sources.redhat.com/gdb/bugs/259
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
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)
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 32
thread 1 32 2
thread 2 34 0
thread 3 34 0
thread 4 34 0
thread 5 34 0
. gdb gdb_6_0-branch
checkout date is '2003-09-26 10:36:05 UTC'
previous date is '2003-09-23 01:02:48 UTC'
. gdb.cp/annota2.exp: annotate-quit
Same analysis as gdb 5.3.
. gdb.mi/mi*-pthreads.exp: check mi_thread_command_set: -thread-select [3456]
PASS -> blank
blank -> PASS
Same analysis as gdb 5.3.92.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (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 10 24
thread 1 26 8
thread 2 31 3
thread 3 33 1
thread 4 33 1
thread 5 34 0
. gdb HEAD
checkout date is '2003-09-26 10:32:21 UTC'
previous date is '2003-09-23 00:57:26 UTC'
. gdb.cp/annota2.exp: annotate-quit
gdb.cp/annota3.exp: annotate-quit
Same analysis as gdb 5.3.
. gdb.base/corefile.exp: up in corefile.exp (reinit)
XPASS -> PASS
David C improved the test script.
. gdb.cp/classes.exp: print (ClassWithEnum::PrivEnum) 42
PASS -> KFAIL
This is a regression in gdb. The KFAIL is:
http://sources.redhat.com/gdb/bugs/826
variables in C++ namespaces have to be enclosed in quotes
This happened with gcc v3 -gstabs+.
gdb.log excerpts:
# gdb.log
# gdb 2003-09-23 00:57:26 UTC
# gcc 3.3.1, binutils 2.14, -gstabs+
print (ClassWithEnum::PrivEnum) 42
$26 = yellow
(gdb) PASS: gdb.cp/classes.exp: print (ClassWithEnum::PrivEnum) 42
print ('ClassWithEnum::PrivEnum') 42
$27 = yellow
(gdb) PASS: gdb.cp/classes.exp: print ('ClassWithEnum::PrivEnum') 42
# gdb.log
# gdb 2003-09-26 10:32:21 UTC
# gcc 3.3.1, binutils 2.14, -gstabs+
print (ClassWithEnum::PrivEnum) 42
A syntax error in expression, near `42'.
(gdb) KFAIL: gdb.cp/classes.exp: print (ClassWithEnum::PrivEnum) 42 (PRMS: gdb/826)
print ('ClassWithEnum::PrivEnum') 42
$26 = yellow
(gdb) PASS: gdb.cp/classes.exp: print ('ClassWithEnum::PrivEnum') 42
. gdb.cp/local.exp: ptype InnerLocal::NestedInnerLocal
FAIL -> KFAIL
@ 113 115 117 119 121 123 125 127 129 131 133 135
This is a regression in gdb. The KFAIL is:
http://sources.redhat.com/gdb/bugs/482
gdb.c++/local.exp: ptype InnerLocal::NestedInnerLocal
This happened with gcc v3 -gstabs+.
gdb.log excerpts:
# gdb.log
# gdb 2003-09-23 00:57:26 UTC
# gcc 3.3.1, binutils 2.14, -gstabs+
ptype InnerLocal::NestedInnerLocal
type = class InnerLocal::NestedInnerLocal {
public:
int nil;
InnerLocal::NestedInnerLocal & operator=(InnerLocal::NestedInnerLocal const&
);
NestedInnerLocal(InnerLocal::NestedInnerLocal const&);
NestedInnerLocal();
int nil_foo(int);
}
(gdb) FAIL: gdb.cp/local.exp: ptype InnerLocal::NestedInnerLocal
# gdb.log
# gdb 2003-09-26 10:32:21 UTC
# gcc 3.3.1, binutils 2.14, -gstabs+
ptype InnerLocal::NestedInnerLocal
There is no field named NestedInnerLocal
(gdb) KFAIL: gdb.cp/local.exp: ptype InnerLocal::NestedInnerLocal (PRMS: gdb/482)
. gdb.cp/namespace.exp: print AAA::c
gdb.cp/namespace.exp: print AAA::xyzq('x')
gdb.cp/namespace.exp: print BBB::CCC::xyzq('x')
gdb.cp/namespace.exp: print C::D::cd
gdb.cp/namespace.exp: print C::cc
gdb.cp/namespace.exp: print E::cde
gdb.cp/namespace.exp: print E::ce
blank -> PASS
blank -> FAIL
David C added some tests. These new tests PASSed with -gdwarf-2
and FAILed with -gstabs+.
gdb.cp/namespace.exp: print F::cXf
gdb.cp/namespace.exp: print F::cXfX
gdb.cp/namespace.exp: print G::Xg
gdb.cp/namespace.exp: print G::XgX
blank -> FAIL
blank -> PASS
David C added some tests. These new tests PASSed with gcc v3
-gdwarf-2. They FAILed with gcc v2 and gcc v3 -gstabs+.
. gdb.mi/mi*-pthreads.exp: check mi_thread_command_set: -thread-select [3456]
PASS -> blank
blank -> PASS
Same analysis as gdb 5.3.92.
. 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 1 33
thread 1 33 1
thread 2 34 0
thread 3 34 0
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, 5.3.92, 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 136 = 1 * 1 * 1 * 4 * (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.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.