gdb, native i686-pc-linux-gnu
Michael Elizabeth Chastain
mec.gnu@mindspring.com
Mon Feb 9 04:51:00 GMT 2004
. Highlights of This Spin
I added gcc tree-ssa-20020619-branch. This branch has two regressions
versus gcc HEAD.
The current tables are always at
http://www.shout.net/~mec/sunday/current/index.html
. Gdb Regression Summary
gdb HEAD 2004-02-07 12:22:55 UTC versus gdb HEAD
gdb/826 gdb/931 gdb/1505 gdb/1512 gdb/1516
. Gcc Regression Summary
gcc 3.3.3-20040131 versus gcc 3.3.2
no regressions
gcc gcc-3_3-branch 2004-02-06 18:35:45 UTC versus gcc 3.3.2
no regressions
gcc gcc-3_4-branch 2004-02-06 18:29:34 UTC versus gcc 3.3.2
gcc/12267 gcc/13708 gcc/13956 gcc/13974
gdb/1537 gdb/1540
classes.exp unanalyzed regressions
gcc HEAD 2004-02-06 18:20:10 UTC versus gcc 3.3.2
gcc/12267 gcc/13708 gcc/13956 gcc/13974
gdb/1537 gdb/1540
classes.exp unanalyzed regressions
gcc tree-ssa-20020619-branch 2004-02-06 18:09:57 versus gcc HEAD 2004-02-06 18:20:10 UTC
gcc/14048 gcc/14049
. Old Bugs Fixed
. gdb HEAD
http://sources.redhat.com/gdb/bugs/1470
ELF_LINK_POINTER_EQUALITY_NEEDED breaks shlib-call.exp
With binutils HEAD, gdb no longer has PLT entries for shared library
functions. But gdb now asks if the user wants to set a pending
breakpoint, so this is okay.
. New Bugs Detected
None.
. PR Count
Query executed 2004-02-09 03:55:54 UTC
1545 matches found
22 analyzed
708 closed
23 feedback
776 open
3 paperwork
13 suspended
1545 TOTAL
. Libiberty Testing
. target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
binutils HEAD 742 tests, 0 failures
gcc gcc-3_3-branch 649 tests, 0 failures
gcc gcc-3_4-branch 742 tests, 0 failures
gcc HEAD 742 tests, 0 failures
gcc tree-ssa-20020619-branch 742 tests, 0 failures
gdb HEAD 742 tests, 0 failures
gdb carlton_dictionary-branch 742 tests, 0 failures
gdb drow-cplus-branch 742 tests, 0 failures
For gcc tests, the test results are with binutils 2.14.
The binutils version should not make a difference.
. Gdb Testing
My tables are at
http://www.shout.net/~mec/sunday/2004-02-07/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-02-02/index.html
. Non-Pass Results
gdb 6.0
suite 6.0 374 non-PASS results
suite HEAD 538 non-PASS results
gdb HEAD
suite HEAD 480 non-PASS results
gdb carlton_dictionary-branch
suite carlton_dictionary-branch 480 non-PASS results
suite HEAD 489 non-PASS results
gdb drow-cplus-branch
suite drow-cplus-branch 702 non-PASS results
suite HEAD 623 non-PASS results
I run each version of gdb with two test suites: the test suite that
comes with that version of gdb and the test suite that comes with
gdb HEAD.
. gdb 6.0
. suite 6.0
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
. gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Fluctuation in test result probably due to a signal handling
race in the command loop.
http://sources.redhat.com/gdb/bugs/544
gdb.c++/annota2.exp: annotate-quit test sometimes fails
. 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, gdb uses
hidden breakpoints in the thread library to track events such as
thread creation and thread destruction.
This causes some programs to behave differently because they
aren't prepared to handle the additional signals caused by the
hidden breakpoints. 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/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 1 29
thread 1 29 1
thread 2 29 1
thread 3 30 0
thread 4 30 0
thread 5 30 0
One configuration had anomalous results with many FAILs.
http://sources.redhat.com/gdb/bugs/1393
FAIL: gdb.threads/schedlock.exp: continue to breakpoint: return to loop (initial)
The log excerpt is:
# gdb.log excerpt
# target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0
# gdb=6.0, suite=6.0
# gcc=2.95.3, as=2.14, ld=2.14, glibc=2.2.93-5-rh
# gformat=stabs+, glevel=2
(gdb) break 41 if arg != 5
Breakpoint 3 at 0x8048590: file /berman/migchain/source/gdb-6.0/gdb/testsuite/gdb.threads/schedlock.c, line 41.
(gdb) continue
Continuing.
Program received signal SIGINT, Interrupt.
[Switching to Thread 24580 (LWP 22629)]
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 ...
. suite HEAD
. gdb.base/langs.exp: break on nonexistent function in langs.exp
PASS -> FAIL
Jeff J improved the test script. gdb 6.0 does not have the
new behavior that the test script requires, so this test
FAILed with gdb 6.0. gdb 6.0 did not regress.
. gdb.base/pending.exp: *
blank -> PASS
blank -> FAIL
Jeff J wrote a new test script.
. gdb.base/shlib-call.exp: set bp in shared library
PASS -> blank
FAIL -> blank
gdb.base/shlib-call.exp: setting breakpoint at shr1
blank -> FAIL
Jeff J improved the test script. gdb 6.0 did not regress.
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.0 suite 6.0.
. gdb.cp/inherit.exp: print g_vE
FAIL -> PASS
Michael C improved the test.
This happened with gcc 3.2-7-rh -gstabs+.
. gdb.cp/overload.exp: print overloadNameSpace(*)*
blank -> PASS
blank -> FAIL
David C added some tests.
. 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 0 30
thread 1 30 0
thread 2 30 0
thread 3 30 0
thread 4 30 0
thread 5 30 0
. gdb HEAD
. suite HEAD
. gdb.base/gdb1250.exp: setting breakpoint at abort
FAIL -> PASS
gdb.base/gdb1250.exp: running to abort in runto
blank -> FAIL
gdb improved its behavior when setting a breakpoint on a
function in an unloaded shared library when there is no PLT
stub for the function. This happened with binutils HEAD.
http://sources.redhat.com/gdb/bugs/1470
ELF_LINK_POINTER_EQUALITY_NEEDED breaks shlib-call.exp
. gdb.base/pending.exp: *
blank -> PASS
Same analysis as gdb 6.0 suite HEAD.
All results were PASS in all configurations.
. gdb.base/shlib-call.exp: set bp in shared library
PASS -> blank
FAIL -> blank
gdb.base/shlib-call.exp: setting breakpoint at shr
blank -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
. gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/inherit.exp: print g_vE
FAIL -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/overload.exp: print overloadNameSpace(*)*
blank -> PASS
Same analysis as gdb 6.0 suite HEAD.
All results were PASS in all configurations.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 10 (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 1 29
thread 1 29 1
thread 2 30 0
thread 3 30 0
thread 4 30 0
thread 5 30 0
. gdb carlton_dictionary-branch
. suite carlton_dictionary-branch
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. 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 12
thread 1 11 3
thread 2 12 2
thread 3 13 1
thread 4 13 1
thread 5 14 0
. suite HEAD
. gdb.base/langs.exp: break on nonexistent function in langs.exp
PASS -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/pending.exp: *
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/shlib-call.exp: set bp in shared library
PASS -> blank
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/overload.exp: print overloadNameSpace(*)*
blank -> PASS
Same analysis as gdb 6.0 suite HEAD.
All results were PASS in all configurations.
. 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 0 14
thread 1 14 0
thread 2 14 0
thread 3 14 0
thread 4 14 0
thread 5 14 0
. gdb drow-cplus-branch
. suite drow-cplus-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 1 13
thread 1 13 1
thread 2 14 0
thread 3 14 0
thread 4 14 0
thread 5 14 0
. suite HEAD
. gdb.base/langs.exp: break on nonexistent function in langs.exp
PASS -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/pending.exp: *
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/shlib-call.exp: set bp in shared library
PASS -> blank
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/inherit.exp: ptype *
FAIL -> PASS
Michael C improved the test script.
. gdb.cp/overload.exp: print overloadNameSpace(*)*
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/virtfunc.exp: ptype *
FAIL -> PASS
Michael C improved the test script.
. 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 13
thread 1 14 0
thread 2 14 0
thread 3 14 0
thread 4 14 0
thread 5 14 0
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
dejagnu => dejagnu 1.4.4
expect => expect 5.39
tcl => tcl 8.4.5
gdb => 6.0, HEAD, carlton_dictionary-branch, drow-cplus-branch
suite => 6.0, carlton_dictionary-branch, drow-cplus-branch, HEAD
cc => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.2, gcc 3.3.3-20040131, gcc gcc-3_3-branch, gcc gcc-3_4-branch, gcc HEAD, gcc tree-ssa-20020619-branch
as => binutils 2.13.90.0.2-rh, binutils 2.14, binutils HEAD
ld => binutils 2.13.90.0.2-rh, binutils 2.14, binutils HEAD
libc => glibc 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count => 146
'target' and 'host' are gnu configuration triples.
'osversion' is the host operating system name, which is additional
information beyond 'host'.
'tcl', 'expect', and 'dejagnu' are host packages to run tests.
'suite' is the version name of the gdb test suite.
'gdb' is a version name.
'cc', 'as', 'ld', and 'libc' are package 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.
as/ld are always matched.
The vendor gcc is available only with vendor as/ld.
The vendor as/ld are tested only with vendor gcc.
I test gdb carlton_dictionary_branch and gdb drow-cplus-branch only
with as/ld from binutils 2.14, not with vendor as/ld or binutils HEAD
as/ld. This means I do not test c_d-b and d-c-b with vendor gcc.
I test each version gdb with its own gdb-test-suite and also with
gdb-test-suite HEAD.
. Package Versions
. This Spin
binutils HEAD 2004-02-06 18:00:45 UTC
gcc tree-ssa-20020619-branch 2004-02-06 18:09:57 UTC
gcc HEAD 2004-02-06 18:20:10 UTC
gcc gcc-3_4-branch 2004-02-06 18:29:34 UTC
gcc gcc-3_3-branch 2004-02-06 18:35:45 UTC
gdb HEAD 2004-02-07 12:22:55 UTC
gdb carlton_dictionary-branch 2004-02-07 12:24:59 UTC
gdb drow-cplus-branch 2004-02-07 12:27:01 UTC
. Last Spin
binutils HEAD 2004-02-01 15:27:25 UTC
gcc HEAD 2004-02-01 15:37:18 UTC
gcc gcc-3_3-branch 2004-02-01 15:44:58 UTC
gcc gcc-3_4-branch 2004-02-01 15:51:06 UTC
gdb HEAD 2004-02-02 10:05:57 UTC
gdb carlton_dictionary-branch 2004-02-02 10:08:17 UTC
gdb drow-cplus-branch 2004-02-02 10:10:16 UTC
. Host Software
. host=i686-pc-linux-gnu, osversion=red-hat-8.0
make 3.79.1
binutils 2.14
gcc 3.3.2
flex 2.5.4
bison 1.875
tcl 8.4.5
expect 5.39
dejagnu 1.4.4
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.8.tar.gz
ftp://ftp.shout.net/pub/users/mec/migbat/migbat-0.8.tar.gz
. Test Bed Changes Since Last Report
I added gcc tree-ssa-20020619-branch.
More information about the Gcc-testresults
mailing list