This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB 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: Thu, 17 Jun 2004 13:34:38 -0400 (EDT)
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
I added gdb 6.1.0.95. It's healthy. The official gdb-6.1.1.tar.bz2
is identical to gdb-6.1.0.95.tar.bz2.
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
not analyzed
gdb HEAD versus gdb 6.1
gdb/1650 gdb/1677
gdb gdb_6_1-branch versus gdb 6.1
gdb gdb 6.1.0.95 versus gdb 6.1
one improvement, gdb.base/pending.exp
no regressions
. Gcc Regression Summary
gcc HEAD versus gcc 3.4.0
gcc/13974 gcc/14049 gcc/14860 gcc/15721
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 gcc-3_3-branch versus gcc 3.3.3
gcc 3.3.4-20040530 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.15
binutils binutils_2-15-branch versus binutils 2.15
no improvements and no regressions
. Old Bugs Fixed Since Last Spin
. gdb gdb_6_1-branch
. gdb.base/pending.exp: continue to resolved breakpoint 2
gdb.base/pending.exp: continue to resolved breakpoint 1
gdb.base/pending.exp: continue to resolved breakpoint 3
gdb had a bug where ignore-count on pending-breakpoint was not
honored. Jim I fixed it on gdb HEAD on 2004-05-05 and Andrew C
imported the fix to gdb gdb_6_1-branch on 2004-06-12.
. gdb HEAD
gdb/thread-db.c:384: internal-error: thread_from_lwp: Assertion `thread_info && thread_info->private->ti_valid' failed.
Someone, probably Jeff J, fixed this bug.
. gcc HEAD
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14048
[3.5 regression] bad debug line numbers near "return" statement, c++
Richard H fixed this bug.
. New Bugs Detected Since Last Spin
. gdb HEAD
http://sources.redhat.com/gdb/bugs/1677
[regression] selftest.exp, crash in lookup_symtab
. suite HEAD
http://sources.redhat.com/gdb/bugs/1678
gdb.mi/mi2-file.exp: ChangeLog, copyright, sync with mi-file.exp
http://sources.redhat.com/gdb/bugs/1679
i386-sse.exp very noisy with gcc 2.95.3
http://sources.redhat.com/gdb/bugs/1680
i386-sse.exp trouble with '{...}'
. PR Count
Query executed 2004-06-16 15:59:13 UTC
1676 matches found
21 analyzed
772 closed
23 feedback
840 open
3 paperwork
17 suspended
1676 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
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-06-13/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-06-06/index.html
. Non-Pass Results
gdb 6.1
suite 6.1 996 non-PASS results
suite HEAD 1034 non-PASS results
gdb 6.1.0.95
suite 6.1.0.95 996 non-PASS results
suite HEAD 1031 non-PASS results
gdb gdb_6_1-banch
suite gdb_6_1-branch 998 non-PASS results
suite HEAD 1031 non-PASS results
gdb HEAD
suite HEAD 1034 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 1005 non-PASS results
suite HEAD 1037 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/structs.exp: value foo<n> returned; return * structs-*
FAIL -> PASS
gdb.base/structs.exp: value foo<n> returned; return 1 structs-tld
KFAIL -> KPASS
This happened with gcc HEAD. This is a code generation change
with gcc HEAD.
The test program looks like this:
struct struct1 fun1() { return foo1; }
main () { ... L1 = fun1(); ... }
The test script sets a breakpoint on fun1, runs to the
breakpoint, and executes 'return foo1'.
gdb says:
The location at which to store the function's return value is unknown.
If you continue, the return value that you specified will be ignored.
Make fun1 return now? (y or n)
The test script says 'y'. fun1 returns. The test script
executes 'next' to get to the next line. The test script
prints L1.
On the last spin, gcc HEAD generated code like this:
auto struct struct1 temp_1;
fun1(&temp_1);
L1 = temp1;
With this code, when gdb ignores the assignment to the return
value of fun1, L1 gets assigned a random value from temp_1.
On this spin, gcc HEAD generates code like this:
fun1(&L1);
With this code, when gdb ignores the assignment to the return
value of fun1, L1 is left with its previous value.
So the test result has improved, and gdb's usability has
actually improved for real programs. But I can't really call
this a bug fix in gcc though. It's more like gcc happens to
generate better code that no longer triggers a bug in the test
script.
. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
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.cp/class2.exp: print *
FAIL -> PASS
Richard H fixed a bug in gcc HEAD.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14048
[3.5 regression] bad debug line numbers near "return" statement, c++
. gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (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.
t0 t1 t2 t3 t4 t5
PASS 4 44 43 44 42 44
FAIL 40 0 1 0 2 0
. gdb 6.1
. suite HEAD
. gdb.arch/i386-sse.exp: *
blank -> ERROR
blank -> WARNING
blank -> PASS
blank -> FAIL
blank -> UNRESOLVED
Jim B wrote a new test script. The test script behaves badly
on my system.
http://sources.redhat.com/gdb/bugs/1679
i386-sse.exp very noisy with gcc 2.95.3
http://sources.redhat.com/gdb/bugs/1680
i386-sse.exp trouble with '{...}'
. gdb.base/shlib-call.exp: *
FAIL -> blank
FAIL -> PASS
Randolph C improved the test script.
. gdb.base/structs.exp: p/c L<n>; call * structs-*
gdb.base/structs.exp: p/c fun<n>(); call * structs-*
gdb.base/structs.exp: value foo<n> finished; return 1 structs-tld
gdb.base/structs.exp: value foo<n> returned; return 1 structs-tld
gdb.base/structs.exp: zed L<n> for finish; return 1 structs-tld
gdb.base/structs.exp: zed L<n> for return; return 1 structs-tld
KPASS -> PASS
gdb.base/structs.exp: return and finish use same convention; return * structs-*
PASS -> blank
gdb.base/structs.exp: return value known implies finish value known; return * structs-*
blank -> PASS
Andrew C improved the test script.
. gdb.base/structs.exp: value foo<n> returned; return * structs-*
FAIL -> PASS
gdb.base/structs.exp: value foo<n> returned; return 1 structs-tld
KFAIL -> KPASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.base/structs.exp: value foo<n> finished; return 1 structs-tld
KPASS -> PASS
Not analyzed, but probably just a combination of the gcc HEAD
code generation change and the structs.exp change.
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/class2.exp: print *
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi2-file.exp: Undefined command "222-file-list-exec-source-files".
blank -> ERROR
gdb.mi/mi2-file.exp: Getting a list of source files.
blank -> UNRESOLVED
Bob R improved the test script. The new test script reports
an ERROR and UNRESOLVED with old versions of gdb, which is okay.
But there are other problems with the test script.
http://sources.redhat.com/gdb/bugs/1678
gdb.mi/mi2-file.exp: ChangeLog, copyright, sync with mi-file.exp
. 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 1 14 13 14 14 14
FAIL 13 0 1 0 0 0
. gdb 6.1.0.95
. suite 6.1.0.95
This is the first spin for gdb 6.1.0.95 suite 6.1.0.95.
Not analyzed.
. suite HEAD
This is the first spin for gdb 6.1.0.95 suite HEAD.
I compared gdb 6.1, gdb 6.1.0.95, and gdb gdb_6_1-branch with
suite HEAD. There is one improvement from gdb 6.1 to gdb 6.1.0.95
and gdb gdb_6_1-branch (gdb.base/pending.exp). There are no
regressions from gdb 6.1 to gdb 6.1.095 and gdb gdb_6_1-branch.
. gdb gdb_6_1-branch
. suite gdb_6_1-branch
. gdb.base/structs.exp: value foo<n> returned; return * structs-*
FAIL -> PASS
gdb.base/structs.exp: value foo<n> returned; return 1 structs-tld
KFAIL -> KPASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/class2.exp: print *
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 10 (slow with kill breakpoint)
blank -> PASS
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 3 40 42 43 43 44
FAIL 41 4 2 1 1 0
. gdb gdb_6_1-branch
. suite HEAD
. gdb.arch/i386-sse.exp: *
blank -> ERROR
blank -> WARNING
blank -> PASS
blank -> FAIL
blank -> UNRESOLVED
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/pending.exp: continue to resolved breakpoint 2
gdb.base/pending.exp: continue to resolved breakpoint 1
gdb.base/pending.exp: continue to resolved breakpoint 3
FAIL -> PASS
Andrew C imported a bug fix from gdb HEAD.
Jim I fixed the bug on gdb HEAD.
. gdb.base/shlib-call.exp: *
FAIL -> blank
FAIL -> PASS
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/structs.exp: p/c L<n>; call * structs-*
gdb.base/structs.exp: p/c fun<n>(); call * structs-*
gdb.base/structs.exp: value foo<n> finished; return 1 structs-tld
gdb.base/structs.exp: value foo<n> returned; return 1 structs-tld
gdb.base/structs.exp: zed L<n> for finish; return 1 structs-tld
gdb.base/structs.exp: zed L<n> for return; return 1 structs-tld
KPASS -> PASS
gdb.base/structs.exp: return and finish use same convention; return * structs-*
PASS -> blank
gdb.base/structs.exp: return value known implies finish value known; return * structs-*
blank -> PASS
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/structs.exp: value foo<n> returned; return * structs-*
FAIL -> PASS
gdb.base/structs.exp: value foo<n> returned; return 1 structs-tld
KFAIL -> KPASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.base/structs.exp: value foo<n> finished; return 1 structs-tld
KPASS -> PASS
Same analysis as gdb 6.1 suite HEAD.
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/class2.exp: print *
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi2-file.exp: Undefined command "222-file-list-exec-source-files".
blank -> ERROR
gdb.mi/mi2-file.exp: Getting a list of source files.
blank -> UNRESOLVED
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 2 14 14 14 14 13
FAIL 12 0 0 0 0 1
. gdb HEAD
. suite HEAD
. gdb.ada/null_record.exp: Undefined command "begin".
ERROR -> blank
gdb.ada/null_record.exp: begin
UNRESOLVED -> blank
gdb.ada/null_record.exp: start
blank -> PASS
Joel B improved the test script.
. gdb.arch/i386-sse.exp: *
blank -> ERROR
blank -> WARNING
blank -> PASS
blank -> FAIL
blank -> UNRESOLVED
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/selftest.exp: *
PASS -> blank
PASS -> FAIL
This is a regression bug in gdb HEAD.
http://sources.redhat.com/gdb/bugs/1677
[regression] selftest.exp, crash in lookup_symtab
. gdb.base/shlib-call.exp: *
FAIL -> blank
FAIL -> PASS
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/structs.exp: p/c L<n>; call * structs-*
gdb.base/structs.exp: p/c fun<n>(); call * structs-*
gdb.base/structs.exp: value foo<n> finished; return 1 structs-tld
gdb.base/structs.exp: value foo<n> returned; return 1 structs-tld
gdb.base/structs.exp: zed L<n> for finish; return 1 structs-tld
gdb.base/structs.exp: zed L<n> for return; return 1 structs-tld
KPASS -> PASS
gdb.base/structs.exp: return and finish use same convention; return * structs-*
KFAIL -> blank
gdb.base/structs.exp: return value known implies finish value known; return * structs-*
blank -> PASS
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/structs.exp: value foo<n> returned; return * structs-*
FAIL -> PASS
gdb.base/structs.exp: value foo<n> returned; return 1 structs-tld
KFAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/class2.exp: print *
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi2-file.exp: Getting a list of source files.
blank -> PASS
blank -> FAIL
Same analysis as gdb 6.1 suite HEAD.
. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
PASS -> FAIL
FAIL -> PASS
gdb.threads/manythreads.exp: stop threads 1
PASS -> FAIL
FAIL -> PASS
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
FAIL -> FAIL
This is a bug in gdb. It happens intermittently.
http://sources.redhat.com/gdb/bugs/1650
manythreads.exp
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
blank -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.threads/print-threads.exp: Running threads (slow with kill breakpoint)
FAIL -> KFAIL
gdb HEAD improved, probably a bug fix by Jeff J.
On the last spin, gdb produced an internal error:
/berman/fsf/_today_/source/gdb/HEAD/src/gdb/thread-db.c:384: internal-error: thread_from_lwp: Assertion `thread_info && thread_info->private->ti_valid' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
On this spin, gdb has no internal error, but it still KFAIL's:
Print 3, thread 4
Print 4, thread 4
Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 16387 (zombie)]
0x00000000 in ?? ()
(gdb) KFAIL: gdb.threads/print-threads.exp: Running threads (slow with kill breakpoint) (zombie thread) (PRMS: gdb/1265)
. 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 42 43 44 39 44
FAIL 35 2 1 0 5 0
. gdb drow_intercu-20040221-branch
. suite drow_intercu-20040221-branch
. gdb.base/structs.exp: value foo<n> returned; return * structs-*
FAIL -> PASS
gdb.base/structs.exp: value foo<n> returned; return 1 structs-tld
KFAIL -> PASS
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
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/class2.exp: print *
FAIL -> PASS
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
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 3 6 14 14 14 14
FAIL 11 8 0 0 0 0
. gdb drow_intercu-20040221-branch
. suite HEAD
. gdb.arch/i386-sse.exp: *
blank -> ERROR
blank -> WARNING
blank -> PASS
blank -> FAIL
blank -> UNRESOLVED
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/shlib-call.exp: *
FAIL -> blank
FAIL -> PASS
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/structs.exp: p/c L<n>; call * structs-*
gdb.base/structs.exp: p/c fun<n>(); call * structs-*
gdb.base/structs.exp: value foo<n> finished; return 1 structs-tld
gdb.base/structs.exp: value foo<n> returned; return 1 structs-tld
gdb.base/structs.exp: zed L<n> for finish; return 1 structs-tld
gdb.base/structs.exp: zed L<n> for return; return 1 structs-tld
KPASS -> PASS
gdb.base/structs.exp: return and finish use same convention; return * structs-*
PASS -> blank
gdb.base/structs.exp: return value known implies finish value known; return * structs-*
blank -> PASS
Same analysis as gdb 6.1 suite HEAD.
. gdb.base/structs.exp: value foo<n> returned; return * structs-*
FAIL -> PASS
gdb.base/structs.exp: value foo<n> returned; return 1 structs-tld
KFAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.1 suite 6.1.
. gdb.cp/class2.exp: print *
FAIL -> PASS
Same analysis as gdb 6.1 suite 6.1.
. gdb.mi/mi2-file.exp: Undefined command "222-file-list-exec-source-files".
blank -> ERROR
gdb.mi/mi2-file.exp: Getting a list of source files.
blank -> UNRESOLVED
Same analysis as gdb 6.1 suite HEAD.
. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
PASS -> FAIL
gdb.threads/manythreads.exp: stop threads 1
PASS -> FAIL
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
FAIL -> FAIL
Same analysis as gdb HEAD suite HEAD.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
blank -> PASS
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 2 13 14 14 13 14
FAIL 12 1 0 0 1 0
. Package Versions
. This Spin
binutils HEAD 2004-06-11 21:28:01 UTC
binutils binutils-2_15-branch 2004-06-11 21:30:38 UTC
gcc HEAD 2004-06-11 21:52:38 UTC
gcc gcc-3_4-branch 2004-06-11 22:01:31 UTC
gcc gcc-3_3-branch 2004-06-11 22:12:00 UTC
gdb HEAD 2004-06-13 05:30:11 UTC
gdb drow_intercu-20040221-branch 2004-06-13 05:37:22 UTC
gdb gdb_6_1-branch 2004-06-13 05:40:39 UTC
. Last Spin
binutils HEAD 2004-06-05 03:35:21 UTC
binutils binutils-2_15-branch 2004-06-05 03:37:56 UTC
gcc HEAD 2004-06-05 03:44:17 UTC
gcc gcc-3_4-branch 2004-06-05 03:52:05 UTC
gcc gcc-3_3-branch 2004-06-05 04:00:24 UTC
gdb HEAD 2004-06-06 19:02:08 UTC
gdb drow_intercu-20040221-branch 2004-06-06 19:08:07 UTC
gdb gdb_6_1-branch 2004-06-06 19:11:05 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, 6.1.0.95, gdb_6_1-branch, HEAD, drow_intercu-20040221-branch
suite => 6.1, 6.1.0.95, 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-20040530, gcc gcc-3_3-branch, gcc 3.4.0, gcc gcc-3_4-branch, gcc HEAD
as => binutils 2.13.90.0.2-rh, binutils 2.15, binutils binutils-2_15-branch, binutils HEAD
ld => binutils 2.13.90.0.2-rh, binutils 2.15, binutils binutils-2_15-branch, binutils HEAD
libc => glibc 2.2.93-5-rh
gformat => dwarf-2, stabs+
glevel => 2
count => 246
'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 6.1.095 suite 6.1.0.95, 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.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 added gdb 6.1.0.95.