This is the mail archive of the
gcc-testresults@gcc.gnu.org
mailing list for the GCC project.
gdb, native i686-pc-linux-gnu
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: gcc-testresults at gcc dot gnu dot org, gdb-testers at sources dot redhat dot com
- Date: Tue, 30 Mar 2004 16:02:49 -0500 (EST)
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
This spin is for 2004-03-20, which was a while ago. I've been busy
with other work.
In this spin, nothing got worse with any binutils, gcc, gdb.
My current tables are always at
http://www.shout.net/~mec/sunday/current/index.html
. Gdb Regression Summary
gdb drow_intercu-20040221-branch versus gdb HEAD
gdb drow-cplus-branch versus gdb HEAD
Not analyzed.
gdb HEAD versus gdb 6.0
gdb/931 gdb/1505 gdb/1512 gdb/1516 gdb/1588
gdb gdb_6_1-branch versus gdb 6.0
gdb/931 gdb/1505 gdb/1512 gdb/1516 gdb/1588
. Gcc Regression Summary
gcc tree-ssa-20020619-branch versus gcc HEAD
gcc/14048 gcc/14049
gcc HEAD versus gcc 3.3.3
gcc/12267 gcc/13708 gcc/13956 gcc/13974
gdb/1537 gdb/1540
gcc gcc-3_4-branch versus gcc 3.3.3
gcc/12267 gcc/13708 gcc/13956 gcc/13974
gdb/1537 gdb/1540
gcc gcc-3_3-branch versus gcc 3.3.3
no improvements and no regressions
. Binutils Regression Summary
binutils HEAD versus binutils 2.14
binutils binutils-2_15-branch versus binutils 2.14
gdb.base/gdb1250.exp unanalyzed regressions
gdb.base/gdb1476.exp unanalyzed regressions
gdb.base/shlib-call.exp unanalyzed regressions
. Old Bugs Fixed Since Last Spin
. gdb gdb_6_1-branch
Someone fixed a bug with gcc 2.95.3 -gdwarf-2 where an MI variable
is created for a local variable which as the same name as a global
enumeration constant. This shows up as an improvement in
gdb.mi/mi-var-display.exp and gdb.mi/mi2-var-display.exp.
The bug happened only with gcc 2.95.3 -gdwarf-2, not with
gcc v3 or gcc 2.95.3 -gstabs+.
David C fixed pr gdb/1553.
http://sources.redhat.com/gdb/bugs/1553
gdb confused in namespace / subclass
. gdb HEAD
Both of the bugs fixed in gdb gdb_6_1-branch are also fixed in
gdb HEAD.
. New Bugs Detected Since Last Spin
None.
. PR Count
Query executed 2004-03-30 20:53:37 UTC
1599 matches found
22 analyzed
744 closed
25 feedback
789 open
3 paperwork
16 suspended
1599 TOTAL
. Libiberty Testing
. target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
binutils binutils-2_15-branch 742 tests, 0 failures
binutils HEAD 745 tests, 0 failures
gcc gcc-3_3-branch 649 tests, 0 failures
gcc gcc-3_4-branch 745 tests, 0 failures
gcc HEAD 745 tests, 0 failures
gcc tree-ssa-20020619-branch 745 tests, 0 failures
gdb HEAD 745 tests, 0 failures
gdb drow-cplus-branch 742 tests, 0 failures
gdb drow_intercu-20040221-branch 742 tests, 0 failures
gdb gdb_6_1-branch 745 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-03-20/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-03-14/index.html
. Non-Pass Results
gdb 6.0
suite 6.0 457 non-PASS results
suite HEAD 626 non-PASS results
gdb gdb_6_1-banch
suite gdb_6_1-branch 443 non-PASS results
suite HEAD 452 non-PASS results
gdb HEAD
suite HEAD 452 non-PASS results
gdb drow-cplus-branch
suite drow-cplus-branch 610 non-PASS results
suite HEAD 627 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 435 non-PASS results
suite HEAD 473 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
PASS -> KFAIL
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
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]
blank -> PASS
PASS -> blank
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/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
blank -> PASS
gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (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 1 37
thread 1 37 1
thread 2 37 1
thread 3 38 0
thread 4 38 0
thread 5 38 0
. gdb 6.0
. suite HEAD
. gdb.base/auxv.exp: *
blank -> WARNING
blank -> PASS
blank -> FAIL
blank -> UNSUPPORTED
Roland M wrote a new test script.
. gdb.base/bigcore.exp: extract next heap
PASS -> blank
gdb.base/bigcore.exp: extract next heap (stop at 50)
blank -> PASS
gdb.base/bigcore.exp: extract prev heap
PASS -> blank
gdb.base/bigcore.exp: extract prev heap (stop at 50)
blank -> PASS
Not analyzed. Probably harmless. I might have changed
the size of the swap space on my test bed.
. gdb.cp/classes.exp: print (ClassWithEnum::PrivEnum) 42
KFAIL -> KFAIL
David C changed the KFAIL From 826 to 1588.
. 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 11
thread 1 12 0
thread 2 11 1
thread 3 12 0
thread 4 12 0
thread 5 12 0
. gdb gdb_6_1-branch
. suite gdb_6_1-branch
. gdb.base/bigcore.exp: extract next heap
PASS -> blank
gdb.base/bigcore.exp: extract next heap (stop at 50)
blank -> PASS
gdb.base/bigcore.exp: extract prev heap
PASS -> blank
gdb.base/bigcore.exp: extract prev heap (stop at 50)
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 6.0.
. gdb.cp/pr-1553.exp: ptype E::F
gdb.cp/pr-1553.exp: ptype c_var
blank -> PASS
blank -> FAIL
David C imported a test script from gdb HEAD.
. gdb.mi/mi-var-display.exp: create local variable bar
gdb.mi/mi-var-display.exp: info type variable bar
gdb.mi/mi-var-display.exp: eval variable bar
gdb.mi/mi-var-display.exp: eval variable bar with new format
gdb.mi/mi-var-display.exp: assing to variable bar
gdb.mi/mi-var-display.exp: eval variable bar with new value
gdb.mi/mi2-var-display.exp: create local variable bar
gdb.mi/mi2-var-display.exp: info type variable bar
gdb.mi/mi2-var-display.exp: eval variable bar
gdb.mi/mi2-var-display.exp: eval variable bar with new format
gdb.mi/mi2-var-display.exp: assing to variable bar
gdb.mi/mi2-var-display.exp: eval variable bar with new value
FAIL -> PASS
Someone, probably Daniel J or David C, fixed a bug in gdb.
This happened with gcc 2.95.3 -gdwarf-2.
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
PASS -> blank
Same analysis as gdb 6.0 suite 6.0.
. 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 32
thread 1 30 8
thread 2 37 1
thread 3 37 1
thread 4 36 2
thread 5 38 0
. gdb gdb_6_1-branch
. suite HEAD
. gdb.base/auxv.exp: *
blank -> WARNING
blank -> PASS
blank -> FAIL
blank -> UNSUPPORTED
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/bigcore.exp: extract next heap
PASS -> blank
gdb.base/bigcore.exp: extract next heap (stop at 50)
blank -> PASS
gdb.base/bigcore.exp: extract prev heap
PASS -> blank
gdb.base/bigcore.exp: extract prev heap (stop at 50)
blank -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/classes.exp: print (ClassWithEnum::PrivEnum) 42
KFAIL -> KFAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/pr-1553.exp: ptype E::F
gdb.cp/pr-1553.exp: ptype c_var
FAIL -> PASS
David C fixed a bug in gdb.
http://sources.redhat.com/gdb/bugs/1553
gdb confused in namespace / subclass
. gdb.mi/mi-var-display.exp: create local variable bar
gdb.mi/mi-var-display.exp: info type variable bar
gdb.mi/mi-var-display.exp: eval variable bar
gdb.mi/mi-var-display.exp: eval variable bar with new format
gdb.mi/mi-var-display.exp: assing to variable bar
gdb.mi/mi-var-display.exp: eval variable bar with new value
gdb.mi/mi2-var-display.exp: create local variable bar
gdb.mi/mi2-var-display.exp: info type variable bar
gdb.mi/mi2-var-display.exp: eval variable bar
gdb.mi/mi2-var-display.exp: eval variable bar with new format
gdb.mi/mi2-var-display.exp: assing to variable bar
gdb.mi/mi2-var-display.exp: eval variable bar with new value
FAIL -> PASS
Same analysis as gdb gdb_6-1-branch suite gdb_6-1-branch.
. 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 11
thread 1 11 1
thread 2 11 1
thread 3 12 0
thread 4 11 1
thread 5 12 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=gdb_6_1-branch, suite=HEAD
# gcc=HEAD, 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 0x80484d7: file /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.threads/schedlock.c, line 41.
(gdb) continue
Continuing.
Program received signal SIGINT, Interrupt.
[Switching to Thread 24580 (LWP 8046)]
0x42028c82 in sigprocmask () from /lib/i686/libc.so.6
(gdb) FAIL: gdb.threads/schedlock.exp: continue to breakpoint: return to loop (initial)
. gdb HEAD
. suite HEAD
. gdb.base/auxv.exp: *
blank -> WARNING
blank -> PASS
blank -> FAIL
blank -> UNSUPPORTED
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/bigcore.exp: extract next heap
PASS -> blank
gdb.base/bigcore.exp: extract next heap (stop at 50)
blank -> PASS
gdb.base/bigcore.exp: extract prev heap
PASS -> blank
gdb.base/bigcore.exp: extract prev heap (stop at 50)
blank -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.cp/classes.exp: print (ClassWithEnum::PrivEnum) 42
KFAIL -> KFAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/pr-1553.exp: ptype E::F
gdb.cp/pr-1553.exp: ptype c_var
FAIL -> PASS
Same analysis as gdb gdb_6_1-branch suite HEAD.
. gdb.mi/mi-var-display.exp: create local variable bar
gdb.mi/mi-var-display.exp: info type variable bar
gdb.mi/mi-var-display.exp: eval variable bar
gdb.mi/mi-var-display.exp: eval variable bar with new format
gdb.mi/mi-var-display.exp: assing to variable bar
gdb.mi/mi-var-display.exp: eval variable bar with new value
gdb.mi/mi2-var-display.exp: create local variable bar
gdb.mi/mi2-var-display.exp: info type variable bar
gdb.mi/mi2-var-display.exp: eval variable bar
gdb.mi/mi2-var-display.exp: eval variable bar with new format
gdb.mi/mi2-var-display.exp: assing to variable bar
gdb.mi/mi2-var-display.exp: eval variable bar with new value
FAIL -> PASS
Same analysis as gdb gdb_6-1-branch suite gdb_6-1-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 3 35
thread 1 38 0
thread 2 37 1
thread 3 35 3
thread 4 35 3
thread 5 38 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 11
thread 1 10 2
thread 2 12 0
thread 3 12 0
thread 4 12 0
thread 5 12 0
. gdb drow-cplus-branch
. suite HEAD
. gdb.base/auxv.exp: *
blank -> WARNING
blank -> PASS
blank -> FAIL
blank -> UNSUPPORTED
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/bigcore.exp: extract next heap
PASS -> blank
gdb.base/bigcore.exp: extract next heap (stop at 50)
blank -> PASS
gdb.base/bigcore.exp: extract prev heap
PASS -> blank
gdb.base/bigcore.exp: extract prev heap (stop at 50)
blank -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/pending.exp: *
blank -> ERROR
blank -> FAIL
PASS -> FAIL
PASS -> UNRESOLVED
FAIL -> blank
FAIL -> PASS
FAIL -> UNRESOLVED
UNRESOLVED -> FAIL
Not analyzed.
. gdb.cp/classes.exp: print (ClassWithEnum::PrivEnum) 42
KFAIL -> KFAIL
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/rtti.exp: Process no longer exists
blank -> ERROR
gdb.cp/rtti.exp: print *obj3
FAIL -> UNRESOLVED
Not analyzed.
. 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 11
thread 1 12 0
thread 2 12 0
thread 3 12 0
thread 4 12 0
thread 5 12 0
. gdb drow_intercu-20040221-branch
. suite drow_intercu-20040221-branch
. gdb.base/bigcore.exp: extract next heap
PASS -> blank
gdb.base/bigcore.exp: extract next heap (stop at 50)
blank -> PASS
gdb.base/bigcore.exp: extract prev heap
PASS -> blank
gdb.base/bigcore.exp: extract prev heap (stop at 50)
blank -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
PASS -> blank
Same analysis as gdb 6.0 suite 6.0.
. 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 10
thread 1 6 6
thread 2 11 1
thread 3 11 1
thread 4 12 0
thread 5 12 0
. gdb drow_intercu-20040221-branch
. suite HEAD
. gdb.base/auxv.exp: *
blank -> WARNING
blank -> PASS
blank -> FAIL
blank -> UNSUPPORTED
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/bigcore.exp: extract next heap
PASS -> blank
gdb.base/bigcore.exp: extract next heap (stop at 50)
blank -> PASS
gdb.base/bigcore.exp: extract prev heap
PASS -> blank
gdb.base/bigcore.exp: extract prev heap (stop at 50)
blank -> PASS
Same analysis as gdb 6.0 suite HEAD.
. gdb.base/pending.exp: *
blank -> ERROR
blank -> FAIL
PASS -> FAIL
PASS -> UNRESOLVED
FAIL -> blank
FAIL -> PASS
FAIL -> UNRESOLVED
UNRESOLVED -> FAIL
Not analyzed.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb 6.0 suite 6.0.
. gdb.cp/classes.exp: print (ClassWithEnum::PrivEnum) 42
KFAIL -> KFAIL
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 10
thread 1 11 1
thread 2 12 0
thread 3 12 0
thread 4 12 0
thread 5 12 0
. Package Versions
. This Spin
binutils HEAD 2004-03-19 17:26:47 UTC
binutils binutils-2_15-branch 2004-03-19 17:29:10 UTC
gcc tree-ssa-20020619-branch 2004-03-19 17:58:10 UTC
gcc HEAD 2004-03-19 18:06:06 UTC
gcc gcc-3_4-branch 2004-03-19 18:11:56 UTC
gcc gcc-3_3-branch 2004-03-19 18:18:14 UTC
gdb HEAD 2004-03-21 00:58:16 UTC
gdb drow-cplus-branch 2004-03-21 01:00:35 UTC
gdb drow_intercu-20040221-branch 2004-03-21 01:02:37 UTC
gdb gdb_6_1-branch 2004-03-21 01:04:44 UTC
. Last Spin
binutils HEAD 2004-03-13 01:51:46 UTC
binutils binutils-2_15-branch 2004-03-13 01:54:24 UTC
gcc tree-ssa-20020619-branch 2004-03-13 02:07:25 UTC
gcc HEAD 2004-03-13 02:15:03 UTC
gcc gcc-3_4-branch 2004-03-13 02:22:26 UTC
gcc gcc-3_3-branch 2004-03-13 02:29:19 UTC
gdb HEAD 2004-03-14 15:04:08 UTC
gdb drow-cplus-branch 2004-03-14 15:06:33 UTC
gdb drow_intercu-20040221-branch 2004-03-14 15:08:45 UTC
gdb gdb_6_1-branch 2004-03-14 15:11:03 UTC
. 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, gdb_6_1-branch, HEAD, drow-cplus-branch, drow_intercu-20040221-branch
suite => 6.0, gdb_6_1-branch, HEAD, drow-cplus-branch, drow_intercu-20040221-branch
cc => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.3, 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 binutils-2_15-branch, binutils HEAD
ld => binutils 2.13.90.0.2-rh, binutils 2.14, binutils binutils-2_15-branch, binutils HEAD
libc => glibc 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count => 186
'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 most configurations only with as binutils 2.14 and ld binutils
2.14. I test gdb 6.0 suite 6.0, gdb gdb_6_1-branch suite gdb_6-1-branch,
and gdb HEAD suite HEAD with the full spectrum of as and ld.
. 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 tweaked the table generator to collapse test names such as
"address 0x12345678" to a generic "address 0xXXXXXXXX".