This is the mail archive of the gdb-testers@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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: Sun, 15 Aug 2004 02:33:39 -0400
Subject: gdb, native i686-pc-linux-gnu

. Highlights of This Spin

This was a quiet spin. There were no new bugs and no bug fixes
in gdb, gcc, and binutils.

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 improvements and regressions

. Gcc Regression Summary

gcc HEAD versus gcc 3.4.1
gcc/13974 gcc/14049
gdb/1656 gdb/1734 gdb/1735

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

None.

. New Bugs Detected Since Last Spin

None.

. PR Count

Query executed 2004-08-14 19:45:07 UTC

1748 matches found
21 analyzed
825 closed
24 feedback
858 open
3 paperwork
17 suspended
1748 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-08-12/index.html

The previous tables are at

http://www.shout.net/~mec/sunday/2004-08-07/index.html

. Non-Pass Results

gdb 6.2
suite 6.2 1482 non-PASS results
suite HEAD 1358 non-PASS results
gdb gdb_6_2-branch
suite gdb_6_2-branch 1482 non-PASS results
suite HEAD 1358 non-PASS results
gdb HEAD
suite HEAD 1355 non-PASS results
gdb drow_intercu-20040221-branch
suite drow_intercu-20040221-branch 1506 non-PASS results
suite HEAD 1372 non-PASS results

. gdb 6.2

. suite 6.2

. 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.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)
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 1 22 22 22 21 22
FAIL 21 0 0 0 1 0

. suite HEAD

. gdb.arch/i386-prologue.exp: check jump_at_beginning prologue end
FAIL -> PASS

Daniel Jacobowitz improved the test script.

. gdb.base/signals.exp: backtrace for 3rd alarm
gdb.base/signals.exp: continue to handle for 3rd alam call (the program exited)
FAIL -> KFAIL

Daniel Jacobowitz changed these results from FAIL to KFAIL.
(It's controversial whether this change is an improvement).

. gdb.cp/annota2.exp: annotate-quit
PASS -> KFAIL
. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL

Same analysis as gdb 6.2 suite 6.2.

. gdb.cp/classes.exp: ptype class vB
gdb.cp/classes.exp: ptype class vC
gdb.cp/classes.exp: ptype class vD
gdb.cp/classes.exp: ptype class vE
FAIL -> PASS
XFAIL -> PASS
gdb.cp/classes.exp: ptype class Foo
PASS -> KFAIL
gdb.cp/classes.exp: ptype obj_with_enum
FAIL -> PASS

Michael Chastain improved the test script.

. gdb.cp/templates.exp: ptype Baz
FAIL -> KFAIL

Daniel Jacobowitz improved the test script.

. gdb.gdb/selftest.exp: step into xmalloc call
PASS -> FAIL
gdb.gdb/selftest.exp: *
blank -> FAIL
PASS -> blank

The test script had a bad change and does not work
with gdb 6.2. This has already been fixed.

. gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
gdb.threads/manythreads.exp: stop threads 1
gdb.threads/manythreads.exp: stop threads 2
FAIL -> PASS

Same analysis as gdb 6.2 suite 6.2.

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 5 5 9 9 10 10
FAIL 5 5 1 1 0 0

. gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
gdb.threads/watchthreads.exp: watchpoint on args[1] hit in thread
PASS -> FAIL
FAIL -> PASS

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/annota2.exp: annotate-quit
KFAIL -> PASS

Same analysis as gdb 6.2 suite 6.2.

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 19 22 22 22 22
FAIL 22 3 0 0 0 0

. gdb gdb_6_2-branch

. suite HEAD

. gdb.arch/i386-prologue.exp: *
gdb.base/signals.exp: *
gdb.cp/classes.exp: *
gdb.cp/templates.exp: *
gdb.gdb/selftest.exp: *
* -> *

Same analyses as gdb 6.2 suite HEAD.

. gdb.cp/annota3.exp: annotate-quit
PASS -> FAIL

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)
blank -> PASS

Same analysis as gdb 6.2 suite 6.2.

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 6 9 9 10 10
FAIL 7 4 1 1 0 0

. gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
gdb.threads/watchthreads.exp: watchpoint on args[0] hit in thread
gdb.threads/watchthreads.exp: watchpoint on args[1] hit in thread
PASS -> FAIL
FAIL -> PASS

Same analysis as gdb 6.2 suite HEAD.

. gdb HEAD

. suite HEAD

. gdb.arch/i386-prologue.exp: *
gdb.base/signals.exp: *
gdb.cp/classes.exp: *
gdb.cp/templates.exp: *
gdb.gdb/selftest.exp: *
* -> *

Same analyses as gdb 6.2 suite HEAD.

. gdb.cp/annota2.exp: annotate-quit
KFAIL -> PASS
gdb.cp/annota3.exp: annotate-quit
FAIL -> PASS

Same analysis as gdb 6.2 suite 6.2.

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 14 10 3 1 0 0
FAIL 8 12 19 21 22 22

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 nothing noteworthy.

. Package Versions

. This Spin

binutils HEAD 2004-08-11 13:49:50 UTC
gcc HEAD 2004-08-11 14:02:52 UTC
gcc gcc-3_4-branch 2004-08-11 14:17:11 UTC
gcc gcc-3_3-branch 2004-08-11 14:32:21 UTC
gdb HEAD 2004-08-12 19:18:47 UTC
gdb drow_intercu-20040221-branch 2004-08-12 19:31:20 UTC
gdb gdb_6_2-branch 2004-08-12 19:37:16 UTC

. Last Spin

binutils HEAD 2004-08-06 15:32:49 UTC
gcc HEAD 2004-08-06 16:03:43 UTC
gcc gcc-3_4-branch 2004-08-06 16:19:34 UTC
gcc gcc-3_3-branch 2004-08-06 16:35:43 UTC
gdb HEAD 2004-08-07 08:51:36 UTC
gdb drow_intercu-20040221-branch 2004-08-07 09:04:45 UTC
gdb gdb_6_2-branch 2004-08-07 09:12:44 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 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 => 126

'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 dropped gdb 6.1.1.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]