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: Michael Chastain <mec dot gnu at mindspring dot com>
- To: gcc-testresults at gcc dot gnu dot org, gdb-testers at sources dot redhat dot com
- Date: Sat, 04 Sep 2004 22:37:00 -0400
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
I added gcc 3.4.2-20040829. I saw no debug info regressions from
gcc 3.4.1 to gcc 3.4.2-20040829.
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 gdb_6_2-branch
no regressions
gdb gdb_6_2-branch versus gdb 6.2
no regressions
. Gcc Regression Summary
gcc HEAD versus gcc 3.4.1
gcc/13974
gdb/1656 gdb/1734 gdb/1742 gdb/1743
gcc 3.4.2-20040829 versus gcc 3.4.1
gcc gcc-3_4-branch versus gcc 3.4.1
no regressions
gcc/13956 has been fixed
gcc 3.4.1 versus gcc 3.3.4
gcc/12267 gcc/13708 gcc/13956
gdb/1537 gdb/1540
gcc gcc-3_3-branch versus gcc 3.3.4
no improvements and no regressions
gcc 3.3.4 versus gcc 2.95.3
not analyzed
. Binutils Regression Summary
binutils HEAD versus binutils 2.15
no improvements and no regressions
. Old Bugs Fixed Since Last Spin
. gdb HEAD
. gdb.base/unload.exp: continuing to end of program
gdb.base/unload.exp: rerun to shared library breakpoint
gdb.base/unload.exp: continuing to end of program second time
FAIL -> PASS
Jeff Johnston fixed a bug in gdb.
. New Bugs Detected Since Last Spin
None.
. PR Count
Query executed 2004-09-04 19:04:08 UTC
1772 matches found
21 analyzed
834 closed
23 feedback
874 open
3 paperwork
17 suspended
1772 TOTAL
. Libiberty Testing
. target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
binutils HEAD 746 tests, 0 failures
gcc gcc-3_3-branch 649 tests, 0 failures
gcc gcc-3_4-branch 745 tests, 0 failures
gcc HEAD 746 tests, 0 failures
gdb HEAD 746 tests, 0 failures
gdb drow_intercu-20040221-branch 745 tests, 0 failures
gdb gdb_6_2-branch 746 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-09-02/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-08-18/index.html
. Non-Pass Results
gdb 6.2
suite 6.2 1485 non-PASS results
suite HEAD 388 non-PASS results
gdb gdb_6_2-branch
suite gdb_6_2-branch 1484 non-PASS results
suite HEAD 385 non-PASS results
gdb HEAD
suite HEAD 384 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 1505 non-PASS results
suite HEAD 407 non-PASS results
. gdb 6.2
. suite 6.2
. 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.threads/manythreads.exp: GDB exits after stopping multithreaded program
gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
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
PASS -> blank
Fluctuation with unknown cause. Probably harmless.
. gdb.threads/schedlock.exp: *
PASS
UNSUPPORTED
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 non-gcc-HEAD configurations except for
the "thread N ran" tests. Here are the counts per thread.
t0 t1 t2 t3 t4 t5
PASS 3 26 26 25 23 26
FAIL 23 0 0 1 3 0
. gdb 6.2
. suite HEAD
. gdb.arch/i386-prologue.exp: skip breakpoint in *
blank -> PASS
Mark Kettenis improved the test script.
. gdb.base/call-rt-st.exp: print *
blank -> PASS
PASS -> blank
Corinna Vinschen improved the test script.
. gdb.base/call-sc.exp: return foo; synchronize pc to main()
blank -> PASS
Paul Gilliam improved the test script.
. gdb.base/sigstep.exp: *
blank -> PASS
blank -> KFAIL
PASS -> blank
Andrew Cagney improved the test script.
. gdb.base/unload.exp: *
gdb.mi/gdb669.exp: *
gdb.mi/mi-basics.exp: *
gdb.mi/mi-break.exp: *
gdb.mi/mi-cli.exp: *
gdb.mi/mi-disassemble.exp: *
gdb.mi/mi-eval.exp: *
gdb.mi/mi-file.exp: *
gdb.mi/mi-pthreads.exp: *
gdb.mi/mi-regs.exp: *
gdb.mi/mi-return.exp: *
gdb.mi/mi-simplerun.exp: *
gdb.mi/mi-stack.exp: *
gdb.mi/mi-stepi.exp: *
gdb.mi/mi-var-block.exp: *
gdb.mi/mi-var-child.exp: *
gdb.mi/mi-var-cmd.exp: *
gdb.mi/mi-var-display.exp: *
gdb.mi/mi-watch.exp: *
gdb.mi/mi2-basics.exp: *
gdb.mi/mi2-break.exp: *
gdb.mi/mi2-cli.exp: *
gdb.mi/mi2-disassemble.exp: *
gdb.mi/mi2-eval.exp: *
gdb.mi/mi2-file.exp: *
gdb.mi/mi2-pthreads.exp: *
gdb.mi/mi2-regs.exp: *
gdb.mi/mi2-return.exp: *
gdb.mi/mi2-simplerun.exp: *
gdb.mi/mi2-stack.exp: *
gdb.mi/mi2-stepi.exp: *
gdb.mi/mi2-var-block.exp: *
gdb.mi/mi2-var-child.exp: *
gdb.mi/mi2-var-cmd.exp: *
gdb.mi/mi2-var-display.exp: *
gdb.mi/mi2-watch.exp: *
gdb.threads/schedlock.exp: *
gdb.threads/thread-specific.exp: *
gdb.threads/watchthreads.exp: *
blank -> PASS
blank -> FAIL
ERROR -> blank
WARNING -> blank
NOTE -> blank
FAIL -> blank
FAIL -> PASS
UNRESOLVED -> blank
UNRESOLVED -> PASS
UNSUPPORTED -> blank
This happened with gcc HEAD.
Michael Chastain fixed the test programs to compile with gcc HEAD.
. gdb.mi/mi-file.exp: Getting a list of source files.
FAIL -> PASS
This happened with gcc v2 and v3, -gstabs+.
Michael Chastain changed the test program by adding an
explicit #include of <stdio.h>. This caused gdb to show a
longer list of source files in response to
file-list-exec-source-files, which changed this result from
FAIL to PASS.
. gdb.threads/bp_in_thread.exp: *
Joel Brobecker wrote a new test script.
. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb 6.2 suite 6.2.
. 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 5 11 12 14 12 14
FAIL 9 3 2 0 2 0
. gdb.threads/staticthreads.exp: *
blank -> PASS
blank -> KFAIL
Andrew Cagney wrote a new test script.
. gdb.threads/thread_check.exp: *
blank -> PASS
blank -> FAIL
Manoj Iyer wrote a new test script.
. gdb.threads/watchthreads.exp: watchpoint on args[0] hit in thread
gdb.threads/watchthreads.exp: first watchpoint on args[0] hit
gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
PASS -> FAIL
http://sources.redhat.com/ml/gdb-testers/2004-q3/msg00071.html
Daniel Jacobowitz wrote:
The main problem is that the test script works if one
watchpoint triggers at a time.
(A) The test script has problems. It doesn't match the
output correctly, and bails out of the main loop too early.
(B) GDB has problems. If a thread creation breakpoint is
hit, and a watchpoint triggers while we are stopping all
threads, then GDB prints "Thread Creation Event - GDB should
not stop!" or something like that. Even if I fix that bug
and make GDB print the watchpoint information, it thinks the
current thread is the one stopped in __nptl_create_event and
prints that thread's location.
. gdb gdb_6_2-branch
. suite gdb_6_2-branch
. gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS
Same analysis as gdb 6.2 suite 6.2.
. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
FAIL -> FAIL
Same analysis as gdb 6.2 suite 6.2.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
PASS -> blank
Same analysis as gdb 6.2 suite 6.2.
. gdb.threads/schedlock.exp: *
PASS
UNSUPPORTED
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 non-gcc-HEAD configurations except for
the "thread N ran" tests. Here are the counts per thread.
t0 t1 t2 t3 t4 t5
PASS 1 25 25 25 25 26
FAIL 25 1 1 1 1 0
. gdb gdb_6_2-branch
. suite HEAD
. gdb.arch/i386-prologue.exp: skip breakpoint in *
gdb.base/call-rt-st.exp: print *
gdb.base/call-sc.exp: return foo; synchronize pc to main()
gdb.base/sigstep.exp: *
gdb.base/unload.exp: *
gdb.mi/gdb669.exp: *
gdb.mi/mi-*.exp: *
gdb.mi/mi2-*.exp: *
gdb.mi/mi-file.exp: Getting a list of source files.
gdb.threads/bp_in_thread.exp: *
gdb.threads/schedlock.exp: *
gdb.threads/staticthreads.exp: *
gdb.threads/thread-specific.exp: *
gdb.threads/thread_check.exp: *
gdb.threads/watchthreads.exp: *
* -> *
Same analyses as gdb 6.2 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.2 suite 6.2.
. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
Same analysis as gdb 6.2 suite 6.2.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
PASS -> blank
blank -> PASS
Same analysis as gdb 6.2 suite 6.2.
. 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 11 13 13 14 14
FAIL 12 3 1 1 0 0
. gdb.threads/watchthreads.exp: watchpoint on args[0] hit in thread
gdb.threads/watchthreads.exp: watchpoint on args[1] hit in thread
gdb.threads/watchthreads.exp: first watchpoint on args[0] hit
gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
PASS -> FAIL
Same analysis as gdb 6.2 suite HEAD.
. gdb HEAD
. suite HEAD
. gdb.arch/i386-prologue.exp: skip breakpoint in *
gdb.base/call-rt-st.exp: print *
gdb.base/call-sc.exp: return foo; synchronize pc to main()
gdb.base/sigstep.exp: *
gdb.base/unload.exp: *
gdb.mi/gdb669.exp: *
gdb.mi/mi-*.exp: *
gdb.mi/mi2-*.exp: *
gdb.threads/bp_in_thread.exp: *
gdb.threads/schedlock.exp: *
gdb.threads/staticthreads.exp: *
gdb.threads/thread-specific.exp: *
gdb.threads/thread_check.exp: *
gdb.threads/watchthreads.exp: *
* -> *
Same analyses as gdb 6.2 suite HEAD.
. gdb.base/unload.exp: continuing to end of program
gdb.base/unload.exp: rerun to shared library breakpoint
gdb.base/unload.exp: continuing to end of program second time
FAIL -> PASS
Jeff Johnston fixed a bug in gdb.
. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
PASS -> FAIL
FAIL -> PASS
FAIL -> FAIL
Same analysis as gdb 6.2 suite 6.2.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
blank -> PASS
Same analysis as gdb 6.2 suite 6.2.
. 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 7 22 28 30 30 30
FAIL 23 8 2 0 0 0
. gdb.threads/watchthreads.exp: watchpoint on args[0] hit in thread
gdb.threads/watchthreads.exp: watchpoint on args[1] hit in thread
gdb.threads/watchthreads.exp: first watchpoint on args[0] hit
gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
PASS -> FAIL
Same analysis as gdb 6.2 suite HEAD.
. gdb drow_intercu-20040221-branch
The last change on this branch was 2004-08-07.
. suite drow_intercu-20040221-branch
I examined the tables and found nothing noteworthy.
. suite HEAD
I examined the tables and found one noteworthy change.
. Package Versions
. This Spin
binutils HEAD 2004-08-31 16:00:38 UTC
gcc HEAD 2004-08-31 16:33:12 UTC
gcc gcc-3_4-branch 2004-08-31 16:49:16 UTC
gcc gcc-3_3-branch 2004-08-31 17:03:07 UTC
gdb HEAD 2004-09-02 09:48:18 UTC
gdb drow_intercu-20040221-branch 2004-09-02 10:01:01 UTC
gdb gdb_6_2-branch 2004-09-02 10:07:35 UTC
. Last Spin
binutils HEAD 2004-08-17 17:45:50 UTC
gcc HEAD 2004-08-17 18:20:02 UTC
gcc gcc-3_4-branch 2004-08-17 18:32:33 UTC
gcc gcc-3_3-branch 2004-08-17 18:44:59 UTC
gdb HEAD 2004-08-18 09:33:40 UTC
gdb drow_intercu-20040221-branch 2004-08-18 09:47:51 UTC
gdb gdb_6_2-branch 2004-08-18 09:55:25 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.2.2, gdb_6_2-branch, HEAD, drow_intercu-20040221-branch
suite => 6.2.2, gdb_6_2-branch, HEAD, drow_intercu-20040221-branch
cc => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.4, gcc gcc-3_3-branch, gcc 3.4.1, gcc 3.4.2-20040829, gcc gcc-3_4-branch, gcc HEAD
as => binutils 2.13.90.0.2-rh, binutils 2.15, binutils HEAD
ld => binutils 2.13.90.0.2-rh, binutils 2.15, 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 6.2 suite 6.2, gdb gdb_6_2-branch suite gdb_6-2-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.15
gcc 3.3.4
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 gcc 3.4.2-20040829.