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: binutils at sources dot redhat dot com, gcc-testresults at gcc dot gnu dot org,gdb-testers at sources dot redhat dot com
- Date: Mon, 24 May 2004 08:13:00 -0400 (EDT)
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
I added binutils 2.15. binutils 2.15 has no significant result
differences from binutils 2.14.92, and binutils 2.15 has no
regressions from binutils 2.14.
I added gcc 3.3.4-20040517. gcc 3.3.4-20040517 has no significant
result differences from gcc 3.3.3 or gcc gcc-3_3-branch.
gcc tree-ssa-20020619-branch has been merged to gcc HEAD. In this
spin, there are no significant result differences between these two
versions of gcc. The branch had two regressions with respect to HEAD,
gcc/14048 and gcc/14049. These bugs are now incorporated in gcc HEAD.
Development has ended on gcc tree-ssa-20020619-branch. There were
no commits to this branch after 2004-05-14 to 2004-05-23. So this
is the last spin for gcc tree-ssa-20020619-branch.
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.arch/i386-prologue.exp: check jump_at_beginning prologue end
gdb.base/call-sc.exp: return foo; return call-sc-tld
gdb.base/call-sc.exp: value foo returned; return call-sc-td
gdb.base/call-sc.exp: value foo returned; return call-sc-tf
gdb.base/call-sc.exp: value foo returned; return call-sc-tld
gdb HEAD versus gdb 6.1
gdb/1444 gdb/1613 gdb/1650
gdb gdb_6_1-branch versus gdb 6.1
no improvements and no regressions
. Gcc Regression Summary
gcc HEAD versus gcc 3.4.0
gcc/13974 gcc/14048 gcc/14049 gcc/14860
gdb/1656
gcc gcc-3_4-branch versus gcc 3.4.0
no improvements and no regressions
gcc 3.4.0 versus gcc 3.3.3
gcc/12267 gcc/13708 gcc/13956
gdb/1537 gdb/1540
gcc 3.3.4-20040517 versus gcc 3.3.3
gcc gcc-3_3-branch versus gcc 3.3.3
no improvements and no regressions
gcc 3.3.3 versus gcc 2.95.3
not analyzed
. Binutils Regression Summary
binutils HEAD versus binutils 2.14
binutils binutils-2_15-branch versus binutils 2.14
binutils 2.15 versus binutils 2.14
binutils 2.14.92 versus binutils 2.14
gdb/1470
gdb no longer has PLT entries for shared library functions
gdb asks if the user wants to set a pending breakpoint
the test script shlib-call.exp needs an update
binutils is okay
. Old Bugs Fixed Since Last Spin
. gdb HEAD
http://sources.redhat.com/gdb/bugs/1613
stepi out of signal handler exits program
partially fixed in gdb HEAD
the PR is still open
. gdb gdb_6_1-branch
http://sources.redhat.com/gdb/bugs/1648
version.in corrupted on gdb_6_1-branch
. New Bugs Detected Since Last Spin
None.
. PR Count
Query executed 2004-05-23 14:43:06 UTC
1656 matches found
21 analyzed
764 closed
23 feedback
828 open
3 paperwork
17 suspended
1656 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_intercu-20040221-branch 745 tests, 0 failures
gdb gdb_6_1-branch 745 tests, 0 failures
For gcc tests, the test results are with binutils 2.15.
The binutils version should not make a difference.
. Gdb Testing
My tables are at
http://www.shout.net/~mec/sunday/2004-05-16/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-05-09/index.html
. Non-Pass Results
gdb 6.1
suite 6.1 1032 non-PASS results
suite HEAD 1064 non-PASS results
gdb gdb_6_1-banch
suite gdb_6_1-branch 1032 non-PASS results
suite HEAD 1067 non-PASS results
gdb HEAD
suite HEAD 1101 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 1043 non-PASS results
suite HEAD 1083 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.1
. suite 6.1
. gdb.base/bigcore.exp: extract next heap
gdb.base/bigcore.exp: extract prev heap
PASS -> blank
gdb.base/bigcore.exp: extract next heap (stop at 50)
gdb.base/bigcore.exp: extract prev heap (stop at 50)
blank -> PASS
Not analyzed. Probably harmless.
. gdb.base/structs.exp: value foo<n> returned; return * structs-*
PASS -> FAIL
KPASS -> KFAIL
This is a bug in the test script. The doco also needs
enhancement.
http://sources.redhat.com/gdb/bugs/1656
if gdb cannot find function return value location, random unitialized value is used
This happened with gcc HEAD. These regressions came from
gcc tree-ssa-20020619-branch, which just merged into gcc HEAD.
I should have noticed this when I first started testing gcc
tree-ssa-20020619-branch, but somehow I missed it.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
. 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.cp/class2.exp: *
PASS -> FAIL
This happened with gcc HEAD. This bug came from gcc
tree-ssa-20020619-branch, which just merged into gcc HEAD.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14048
[3.5 regression] bad debug line numbers near "return" statement, c++
. gdb.cp/local.exp: ptype Local
gdb.cp/local.exp: ptype l
gdb.mi/mi-var-block.exp: create local variable foo {2}
gdb.mi/mi-var-block.exp: update all vars: cb foo changed
gdb.mi/mi-var-block.exp: update foo: did not change
gdb.mi/mi-var-block.exp: delete var foo {2}
gdb.mi/mi2-var-block.exp: update all vars: cb foo changed
gdb.mi/mi2-var-block.exp: create local variable foo {2}
gdb.mi/mi2-var-block.exp: update foo: did not change
gdb.mi/mi2-var-block.exp: delete var foo {2}
PASS -> FAIL
This happened with gcc HEAD. These bugs came from
gcc tree-ssa-20020619-branch, which just merged into gcc HEAD.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14049
[3.5 regression] bad debug block info, dwarf-2, c++
. gdb.mi/mi-until.exp: until after while loop
gdb.mi/mi2-until.exp: until after while loop
PASS -> FAIL
This happened with gcc HEAD. This bug looks like another
manifestation of gcc/13974, but might actually be a different
bug.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13974
[3.5 regression] bad line marker in debug info
. 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.
t0 t1 t2 t3 t4 t5
PASS 12 81 77 81 77 82
FAIL 70 1 5 1 5 0
. gdb 6.1
. suite HEAD
. gdb.ada/null_record.exp: Ada compilation failed: *: Ada compiler not installed on this system
blank -> UNSUPPORTED
gdb.ada/null_record.exp: *
ERROR -> blank
FAIL -> blank
UNRESOLVED -> blank
This happened with gcc HEAD. gcc HEAD lost its Ada support
with the merge from gcc tree-ssa-200206-19-branch.
. gdb.base/auxv.exp: *
blank -> WARNING
PASS -> blank
PASS -> FAIL
PASS -> UNSUPPORTED
FAIL -> UNSUPPORTED
This is a bug in the test script.
http://sources.redhat.com/gdb/bugs/1647
gdb.base/auxv.exp, incomplete input consumption
The bug happened on the last spin, but did not happen on this
spin.
. gdb.base/bigcore.exp: tbreak 202
blank -> PASS
gdb.base/bigcore.exp: check core size (system does not support large corefiles)
blank -> XFAIL
gdb.base/bigcore.exp: *
PASS -> blank
FAIL -> blank
Daniel J changed the test script. Now it gives an XFAIL on my
system, which is correct. I have bytes_allocated of
3084865568 and a core file size of 2046103552. My system is
native i686-pc-linux-gnu, red hat 8.0, kernel 2.4.18-14-rh,
glibc 2.2.93-5-rh.
. gdb.base/gdb1476.exp: *
PASS -> blank
Andrew C deleted this test script. gdb.base/signull.exp
supersedes this test script.
. gdb.base/signals.exp: continue to func1
XFAIL -> FAIL
gdb.base/signals.exp: extra continue to func 1
PASS -> blank
gdb.base/signals.exp: next to 2nd alarm (1)
PASS -> blank
gdb.base/signals.exp: next to 2nd alarm
blank -> PASS
Andrew C rewrote a tricky part of the test script.
I did not analyze this.
. gdb.base/signull.exp: *
blank -> PASS
Andrew C wrote a new test script.
. gdb.base/sigstep.exp: next out of handler (program exited)
gdb.base/sigstep.exp: nexti into signal trampoline (program exited)
gdb.base/sigstep.exp: step out of handler (program exited)
KFAIL -> FAIL
Andrew C removed some KFAIL cases from the test script.
. gdb.base/structs.exp: value foo<n> returned; return * structs-*
PASS -> FAIL
KPASS -> KFAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/class2.exp: *
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/local.exp: ptype Local
gdb.cp/local.exp: ptype l
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi-until.exp: until after while loop
gdb.mi/mi2-until.exp: until after while loop
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi-var-block.exp: create local variable foo {2}
gdb.mi/mi-var-block.exp: delete var foo {2}
gdb.mi/mi-var-block.exp: update all vars: cb foo changed
gdb.mi/mi-var-block.exp: update foo: did not change
gdb.mi/mi2-var-block.exp: create local variable foo {2}
gdb.mi/mi2-var-block.exp: delete var foo {2}
gdb.mi/mi2-var-block.exp: update all vars: cb foo changed
gdb.mi/mi2-var-block.exp: update foo: did not change
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.threads/print-threads.exp: *
* -> *
This test script is useless in suite HEAD.
http://sources.redhat.com/gdb/bugs/1636
manythreads.exp issues async ^C that spills onto next 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.
t0 t1 t2 t3 t4 t5
PASS 3 31 32 32 32 32
FAIL 29 1 0 0 0 0
. gdb gdb_6_1-branch
. suite gdb_6_1-branch
. gdb.base/bigcore.exp: extract next heap
gdb.base/bigcore.exp: extract prev heap
PASS -> blank
gdb.base/bigcore.exp: extract next heap (stop at 50)
gdb.base/bigcore.exp: extract prev heap (stop at 50)
blank -> PASS
Not analyzed. Probably harmless.
. gdb.base/selftest.exp: printed version as string
blank -> PASS
gdb.base/selftest.exp: printed version
FAIL -> blank
Michael C fixed a bug in the gdb file version.in.
http://sources.redhat.com/gdb/bugs/1648
version.in corrupted on gdb_6_1-branch
. gdb.base/structs.exp: value foo<n> returned; return * structs-*
PASS -> FAIL
KPASS -> KFAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/class2.exp: *
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/local.exp: ptype Local
gdb.cp/local.exp: ptype l
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi-until.exp: until after while loop
gdb.mi/mi2-until.exp: until after while loop
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi-var-block.exp: create local variable foo {2}
gdb.mi/mi-var-block.exp: delete var foo {2}
gdb.mi/mi-var-block.exp: update all vars: cb foo changed
gdb.mi/mi-var-block.exp: update foo: did not change
gdb.mi/mi2-var-block.exp: create local variable foo {2}
gdb.mi/mi2-var-block.exp: delete var foo {2}
gdb.mi/mi2-var-block.exp: update all vars: cb foo changed
gdb.mi/mi2-var-block.exp: update foo: did not change
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. 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.
t0 t1 t2 t3 t4 t5
PASS 10 76 78 77 77 82
FAIL 72 6 4 5 5 0
. gdb gdb_6_1-branch
. suite HEAD
. gdb.ada/null_record.exp: Ada compilation failed: *: Ada compiler not installed on this system
blank -> UNSUPPORTED
gdb.ada/null_record.exp: *
ERROR -> blank
FAIL -> blank
UNRESOLVED -> blank
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/bigcore.exp: tbreak 202
blank -> PASS
gdb.base/bigcore.exp: check core size (system does not support large corefiles)
blank -> XFAIL
gdb.base/bigcore.exp: *
PASS -> blank
FAIL -> blank
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/gdb1476.exp: *
PASS -> blank
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/selftest.exp: printed version as string
blank -> PASS
gdb.base/selftest.exp: printed version
FAIL -> blank
Same analysis as gdb gdb_6_1-branch suite gdb gdb_6_1-branch.
. gdb.base/signals.exp: continue to func1
XFAIL -> FAIL
gdb.base/signals.exp: extra continue to func 1
PASS -> blank
gdb.base/signals.exp: next to 2nd alarm (1)
PASS -> blank
gdb.base/signals.exp: next to 2nd alarm
blank -> PASS
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/signull.exp: *
blank -> PASS
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/sigstep.exp: next out of handler (program exited)
gdb.base/sigstep.exp: nexti into signal trampoline (program exited)
gdb.base/sigstep.exp: step out of handler (program exited)
KFAIL -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/structs.exp: value foo<n> returned; return * structs-*
PASS -> FAIL
KPASS -> KFAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/class2.exp: *
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/local.exp: ptype Local
gdb.cp/local.exp: ptype l
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi-until.exp: until after while loop
gdb.mi/mi2-until.exp: until after while loop
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi-var-block.exp: create local variable foo {2}
gdb.mi/mi-var-block.exp: delete var foo {2}
gdb.mi/mi-var-block.exp: update all vars: cb foo changed
gdb.mi/mi-var-block.exp: update foo: did not change
gdb.mi/mi2-var-block.exp: create local variable foo {2}
gdb.mi/mi2-var-block.exp: delete var foo {2}
gdb.mi/mi2-var-block.exp: update all vars: cb foo changed
gdb.mi/mi2-var-block.exp: update foo: did not change
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. 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.
t0 t1 t2 t3 t4 t5
PASS 6 31 31 30 29 32
FAIL 26 1 1 2 3 0
. gdb HEAD
. suite HEAD
. gdb.ada/null_record.exp: Ada compilation failed: *: Ada compiler not installed on this system
blank -> UNSUPPORTED
gdb.ada/null_record.exp: *
ERROR -> blank
FAIL -> blank
UNRESOLVED -> blank
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/auxv.exp: *
blank -> PASS
WARNING-> blank
FAIL -> PASS
UNSUPPORTED -> PASS
UNSUPPORTED -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/bigcore.exp: tbreak 202
blank -> PASS
gdb.base/bigcore.exp: check core size (system does not support large corefiles)
blank -> XFAIL
gdb.base/bigcore.exp: *
PASS -> blank
FAIL -> blank
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/gdb1476.exp: *
PASS -> blank
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/signals.exp: continue to func1
XFAIL -> PASS
gdb.base/signals.exp: extra continue to func 1
PASS -> blank
gdb.base/signals.exp: next to 2nd alarm (1)
PASS -> blank
gdb.base/signals.exp: next to 2nd alarm
blank -> PASS
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/signull.exp: *
blank -> PASS
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/sigstep.exp: nexti into signal trampoline
gdb.base/sigstep.exp: stepi into signal trampoline
KFAIL -> PASS
Andrew C removed some KFAIL cases from the test script.
Also, someone improved gdb.
http://sources.redhat.com/gdb/bugs/1613
stepi out of signal handler exits program
. gdb.base/structs.exp: value foo<n> returned; return * structs-*
PASS -> FAIL
KPASS -> KFAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/class2.exp: *
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/local.exp: ptype Local
gdb.cp/local.exp: ptype l
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi-until.exp: until after while loop
gdb.mi/mi2-until.exp: until after while loop
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi-var-block.exp: create local variable foo {2}
gdb.mi/mi-var-block.exp: delete var foo {2}
gdb.mi/mi-var-block.exp: update all vars: cb foo changed
gdb.mi/mi-var-block.exp: update foo: did not change
gdb.mi/mi2-var-block.exp: create local variable foo {2}
gdb.mi/mi2-var-block.exp: delete var foo {2}
gdb.mi/mi2-var-block.exp: update all vars: cb foo changed
gdb.mi/mi2-var-block.exp: update foo: did not change
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
blank -> PASS
PASS -> blank
gdb.threads/manythreads.exp: stop threads 1 (GDB internal error)
gdb.threads/manythreads.exp: stop threads 2 (GDB internal error)
blank -> FAIL
FAIL -> blank
This is a bug in gdb. It happens intermittently.
http://sources.redhat.com/gdb/bugs/1650
manythreads.exp
. gdb.threads/print-threads.exp: *
* -> *
Same analysis as gdb 6.1 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.
t0 t1 t2 t3 t4 t5
PASS 15 81 81 80 72 82
FAIL 67 1 1 2 10 0
. gdb drow_intercu-20040221-branch
. suite drow_intercu-20040221-branch
. gdb.ada/null_record.exp: Ada compilation failed: *: Ada compiler not installed on this system
blank -> UNSUPPORTED
gdb.ada/null_record.exp: *
ERROR -> blank
FAIL -> blank
UNRESOLVED -> blank
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/bigcore.exp: extract next heap
gdb.base/bigcore.exp: extract prev heap
PASS -> blank
gdb.base/bigcore.exp: extract next heap (stop at 50)
gdb.base/bigcore.exp: extract prev heap (stop at 50)
blank -> PASS
Not analyzed. Probably harmless.
. gdb.base/structs.exp: value foo<n> returned; return * structs-*
PASS -> FAIL
KPASS -> KFAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/class2.exp: *
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/local.exp: ptype Local
gdb.cp/local.exp: ptype l
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi-until.exp: until after while loop
gdb.mi/mi2-until.exp: until after while loop
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi-var-block.exp: create local variable foo {2}
gdb.mi/mi-var-block.exp: delete var foo {2}
gdb.mi/mi-var-block.exp: update all vars: cb foo changed
gdb.mi/mi-var-block.exp: update foo: did not change
gdb.mi/mi2-var-block.exp: create local variable foo {2}
gdb.mi/mi2-var-block.exp: delete var foo {2}
gdb.mi/mi2-var-block.exp: update all vars: cb foo changed
gdb.mi/mi2-var-block.exp: update foo: did not change
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
blank -> PASS
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.
t0 t1 t2 t3 t4 t5
PASS 9 19 28 30 30 32
FAIL 23 13 4 2 2 0
. gdb drow_intercu-20040221-branch
. suite HEAD
. gdb.ada/null_record.exp: Ada compilation failed: *: Ada compiler not installed on this system
blank -> UNSUPPORTED
gdb.ada/null_record.exp: *
ERROR -> blank
FAIL -> blank
UNRESOLVED -> blank
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/bigcore.exp: tbreak 202
blank -> PASS
gdb.base/bigcore.exp: check core size (system does not support large corefiles)
blank -> XFAIL
gdb.base/bigcore.exp: *
PASS -> blank
FAIL -> blank
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/gdb1476.exp: *
PASS -> blank
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/signals.exp: continue to func1
XFAIL -> FAIL
gdb.base/signals.exp: extra continue to func 1
PASS -> blank
gdb.base/signals.exp: next to 2nd alarm (1)
PASS -> blank
gdb.base/signals.exp: next to 2nd alarm
blank -> PASS
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/signull.exp: *
blank -> PASS
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/sigstep.exp: nexti into signal trampoline (program exited)
gdb.base/sigstep.exp: stepi into signal trampoline (program exited)
KFAIL -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/structs.exp: value foo<n> returned; return * structs-*
PASS -> FAIL
KPASS -> KFAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/class2.exp: *
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/local.exp: ptype Local
gdb.cp/local.exp: ptype l
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi-until.exp: until after while loop
gdb.mi/mi2-until.exp: until after while loop
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi-var-block.exp: create local variable foo {2}
gdb.mi/mi-var-block.exp: delete var foo {2}
gdb.mi/mi-var-block.exp: update all vars: cb foo changed
gdb.mi/mi-var-block.exp: update foo: did not change
gdb.mi/mi2-var-block.exp: create local variable foo {2}
gdb.mi/mi2-var-block.exp: delete var foo {2}
gdb.mi/mi2-var-block.exp: update all vars: cb foo changed
gdb.mi/mi2-var-block.exp: update foo: did not change
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
blank -> PASS
PASS -> blank
gdb.threads/manythreads.exp: stop threads 1 (GDB internal error)
gdb.threads/manythreads.exp: stop threads 2 (GDB internal error)
blank -> FAIL
FAIL -> blank
Same analysis as gdb HEAD suite HEAD.
. gdb.threads/print-threads.exp: *
* -> *
Same analysis as gdb 6.1 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.
t0 t1 t2 t3 t4 t5
PASS 10 29 28 30 28 32
FAIL 22 3 4 2 4 0
. Package Versions
. This Spin
binutils HEAD 2004-05-14 20:46:24 UTC
binutils binutils-2_15-branch 2004-05-14 20:48:29 UTC
gcc tree-ssa-20020619-branch 2004-05-14 21:18:38 UTC
gcc HEAD 2004-05-14 21:34:48 UTC
gcc gcc-3_4-branch 2004-05-14 21:40:51 UTC
gcc gcc-3_3-branch 2004-05-14 21:47:23 UTC
gdb HEAD 2004-05-16 15:12:49 UTC
gdb drow_intercu-20040221-branch 2004-05-16 15:17:28 UTC
gdb gdb_6_1-branch 2004-05-16 15:19:55 UTC
. Last Spin
binutils HEAD 2004-05-07 11:18:29 UTC
binutils binutils-2_15-branch 2004-05-07 11:20:25 UTC
gcc tree-ssa-20020619-branch 2004-05-07 11:45:33 UTC
gcc HEAD 2004-05-07 11:56:13 UTC
gcc gcc-3_4-branch 2004-05-07 12:06:39 UTC
gcc gcc-3_3-branch 2004-05-07 12:20:08 UTC
gdb HEAD 2004-05-10 00:22:49 UTC
gdb drow_intercu-20040221-branch 2004-05-10 00:27:23 UTC
gdb gdb_6_1-branch 2004-05-10 01:52:27 UTC
. Test Matrix
target => native
host => i686-pc-linux-gnu
osversion => red-hat-8.0
dejagnu => dejagnu 1.4.4
expect => expect 5.41
tcl => tcl 8.4.6
gdb => 6.1, gdb_6_1-branch, HEAD, drow_intercu-20040221-branch
suite => 6.1, gdb_6_1-branch, HEAD, drow_intercu-20040221-branch
cc => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.3, gcc 3.3.4-20040517, gcc gcc-3_3-branch, gcc 3.4.0, gcc gcc-3_4-branch, gcc HEAD, gcc tree-ssa-20020619-branch
as => binutils 2.13.90.0.2-rh, binutils 2.14, binutils 2.14.92, binutils 2.15, binutils binutils-2_15-branch, binutils HEAD
ld => binutils 2.13.90.0.2-rh, binutils 2.14, binutils 2.14.92, binutils 2.15, binutils binutils-2_15-branch, binutils HEAD
libc => glibc 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count => 374
'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 6.1 suite 6.1, gdb gdb_6_1-branch suite gdb_6-1-branch, and
gdb HEAD suite HEAD with the full spectrum of as and ld. I test other
gdb/suite configurations only with as binutils 2.14 + ld binutils
2.14 and as binutils 2.15 + ld binutils 2.15.
. Host Software
. host=i686-pc-linux-gnu, osversion=red-hat-8.0
make 3.79.1
binutils 2.14
gcc 3.3.3
flex 2.5.4
bison 1.875
texinfo 4.7
tcl 8.4.6
expect 5.41
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 dropped binutils 2.14.91.
I added binutils 2.15.
This is the last spin for binutils 2.14 and binutils 2.14.92.
I added gcc 3.3.4-20040517.
This is the last spin for gcc tree-ssa-20020619-branch.