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: Thu, 14 Oct 2004 08:18:09 -0400
- Subject: gdb, native i686-pc-linux-gnu
. Highlights of This Spin
I added -feliminate-dwarf2-dups. With dwarf-2 debug format, I run
configurations with and without this flag, and there is a series of
tables for side-by-side comparisons. gdb is healthy with this flag,
to the extent that the test suite exercises it.
gdb.asm/asm-source.exp has a problem: it passes
-feliminate-dwarf2-dups to the assembler and the assembler blows up.
Aside from that problem, there are no significant differences between
"" and "-feliminate-dwarf-dups".
-feliminate-dwarf2-dups did not work with gcc 2.95.3 or gcc 3.2-7-rh.
It worked fine with gcc 3.3.4 and later. Also,
-feliminate-dwarf2-dups did not work with gdb 6.2.1. It worked fine
with gdb HEAD and gdb drow_intercu-20040221-branch.
I added gcc 3.3.5. It's healthy.
binutils binutils-2_15-branch had some more activity. I assume there
are still no more releases planned from this branch, so I did not test
it.
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
no improvements and no regressions
gdb HEAD versus gdb 6.2.1
several improvements and no regressions
. Gcc Regression Summary
gcc HEAD versus gcc 3.4.2
gdb/1656 gdb/1734 gdb/1742
gcc gcc-3_4-branch versus gcc 3.4.2
no improvements and no regressions
gcc 3.4.2 versus gcc 3.3.4
gcc/12267 gcc/13708
gdb/1537 gdb/1540
gcc gcc-3_3-branch versus gcc 3.3.4
gcc 3.3.5 versus gcc 3.3.4
gcc 3.3.5-20040918 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
. gcc HEAD
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13974
[4.0 regression] bad line marker in debug info
Jan Hubicka fixed this bug.
. New Bugs Detected Since Last Spin
None.
. PR Count
Query executed 2004-09-13 16:55:56 UTC
1790 matches found
22 analyzed
842 closed
23 feedback
883 open
3 paperwork
17 suspended
1790 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 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-10-09/index.html
The previous tables are at
http://www.shout.net/~mec/sunday/2004-09-29/index.html
. Non-Pass Results
suite 6.2.1
suite 6.2.1 1477 non-PASS results
suite HEAD 384 non-PASS results
gdb HEAD
suite HEAD 415 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 410 non-PASS results
suite HEAD 412 non-PASS results
. gdb 6.2.1
. suite 6.2.1
. gdb.mi/mi-until.exp: until after current function
gdb.mi2/mi2-until.exp: until after current function
FAIL -> PASS
This happened with gcc HEAD -gdwarf-2 and gcc HEAD -gstabs+.
Jan Hubicka fixed a bug in gcc HEAD.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13974
[4.0 regression] bad line marker in debug info
. 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
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)
PASS -> blank
blank -> PASS
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 0 30 30 30 30 30
FAIL 30 0 0 0 0 0
. gdb 6.2.1
. suite HEAD
. 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-until.exp: until after current function
gdb.mi2/mi2-until.exp: until after current function
FAIL -> PASS
Same analysis as gdb 6.2.1 suite 6.2.1.
. 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.1 suite 6.2.1.
. 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 14 15 15 16
FAIL 11 5 2 1 1 0
. gdb HEAD
. suite HEAD
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL
Same analysis as gdb 6.2.1 suite HEAD.
. gdb.mi/mi-until.exp: until after current function
gdb.mi2/mi2-until.exp: until after current function
FAIL -> PASS
Same analysis as gdb 6.2.1 suite 6.2.1.
. 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.1 suite 6.2.1.
. gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (slow with kill breakpoint)
PASS -> blank
blank -> PASS
Same analysis as gdb 6.2.1 suite HEAD.
. 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 44 46 47 48
FAIL 39 6 4 2 1 0
. gdb drow_intercu-20040221-branch
The last change on this branch was 2004-09-21.
. suite drow_intercu-20040221-branch
I examined the tables and found nothing noteworthy.
. suite HEAD
I examined the tables and found nothing noteworthy.
. Package Versions
. This Spin
binutils HEAD 2004-10-08 16:22:45 UTC
gcc HEAD 2004-10-08 16:52:13 UTC
gcc gcc-3_4-branch 2004-10-08 17:13:42 UTC
gcc gcc-3_3-branch 2004-10-08 17:26:34 UTC
gdb HEAD 2004-10-09 15:27:44 UTC
gdb drow_intercu-20040221-branch 2004-10-09 15:43:22 UTC
. Last Spin
binutils HEAD 2004-09-28 17:09:39 UTC
gcc HEAD 2004-09-28 17:25:19 UTC
gcc gcc-3_4-branch 2004-09-28 17:41:56 UTC
gcc gcc-3_3-branch 2004-09-28 17:58:33 UTC
gdb HEAD 2004-09-29 13:58:01 UTC
gdb drow_intercu-20040221-branch 2004-09-29 14:12:55 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.1, HEAD, drow_intercu-20040221-branch
suite => 6.2.1, HEAD, drow_intercu-20040221-branch
cc => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.4, gcc 3.3.5-20040918, gcc 3.3.5, gcc gcc-3_3-branch, gcc 3.4.2, 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
ed2dup => no, yes
count => 144
'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 tested gdb 6.2.1 suite 6.2.1 and gdb HEAD suite HEAD with the full
spectrum of as and ld. I tested other gdb/suite configurations with
just as binutils 2.15 + ld binutils 2.15.
I test with ed2dup=yes (-feliminate-dwarf2-dup) with these
configurations: dwarf-2, gcc 3.3 or later, gdb HEAD or
gdb drow_intercu-20040221-branch.
. 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
This is the software I use to build gdb and run the test suite. But
it is not the toolchain I use to build the test programs that run
under gdb.
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 another dimension for -feliminate-dwarf2-dups.
I added gcc 3.3.5. I did not see a tarball on ftp.gnu.org yet,
so I got it from sources.redhat.com.
This is the last spin for gcc 3.3.4.
This is the last spin for gcc 3.3.5-20040918.
Daniel Jacobowitz told me that gdb drow_intercu-20040221-branch has
been completely merged into gdb HEAD. So this is the last spin for
gdb drow_intercu-20040221-branch, as long as there are no more
commits to the branch. The last commit was 2004-09-21.