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]

sunday project, gdb, 2003-02-28


Highlights of this report:

. No new bugs detected in gdb or the gdb test suite.

. There are no regressions in the gdb test suite from gcc 3.2.2 to gcc
  gcc-3_2-branch%20030227.

. There are several regressions in the gdb test suite from gcc 3.2.2
  to gcc gcc-3_3-branch%20030227.  Specicially:
  
    gdb=5.3 gformat=stabs+ glevel=2
      gdb.c++/inherit.exp
      gdb.c++/local.exp
    gdb=HEAD gformat=stabs+ glevel=2
      gdb.c++/inherit.exp
      gdb.c++/local.exp

  I will investigate these.

My tables are here:

  http://www.shout.net/~mec/sunday/2003-02-28/index.html

Michael C

. Old Bugs Fixed

  Daniel J improved ax-gdb.c to handle LOC_COMPUTED and
  LOC_COMPUTED_ARG.  This fixed:
    FAIL: gdb.trace/packetlen.exp: setup collect actions

. New Bugs Detected

  None.

. PR count

  Query executed 2003-03-01T15:52:42Z

  1104 matches found
    14 analyzed
   461 closed
    11 feedback
   609 open
     1 paperwork
     8 suspended
  1104 TOTAL

. Libiberty Testing

  . target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
      binutils HEAD                             649 tests, 0 failures
      gcc 2.95.3, binutils HEAD                 All 616 tests passed
      gcc 3.2.2, binutils HEAD                  All 648 tests passed
      gcc gcc-3_2-branch, binutils 2.13.2.1     All 648 tests passed
      gcc gcc-3_2-branch, binutils HEAD         All 648 tests passed
      gcc gcc-3_2-branch, binutils vendor       All 648 tests passed
      gcc gcc-3_3-branch, binutils 2.13.2.1     649 tests, 0 failures
      gcc gcc-3_3-branch, binutils HEAD         649 tests, 0 failures
      gcc gcc-3_3-branch, binutils vendor       649 tests, 0 failures
      gcc HEAD, binutils 2.13.2.1               649 tests, 0 failures
      gcc HEAD, binutils HEAD                   649 tests, 0 failures
      gcc HEAD, binutils vendor                 649 tests, 0 failures
      gdb HEAD                                  649 tests, 0 failures

. Gdb Testing

  My tables are at:

    http://www.shout.net/~mec/sunday/2003-02-28/index.html

  The previous report was 2003-02-23:

    http://www.shout.net/~mec/sunday/2003-02-23/Analysis.txt

  . Counts

    gdb 5.3:             0 test aborts, 329 non-PASS results
    gdb HEAD:            0 test aborts, 267 non-PASS results

    A non-PASS result is any result except PASS.  This includes ERROR,
    WARNING, NOTE, FAIL, KPASS, KFAIL, XPASS, XFAIL, UNRESOLVED,
    UNTESTED, UNSUPPORTED, and unknown results.

  . 5.3

    . gdb.c++/annota2.exp: annotate-quit

	pr gdb/544: gdb.c++/annota2.exp: annotate-quit test sometimes fails
	http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=544

	Fluctuation in test result probably due to a signal handling
	race in the command loop.

    . gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily

	pr gdb/568: GDB confused by messily-exiting multi-threaded programs
	http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=568

	Jim B thinks that this test may depend on a race condition:

	  http://sources.redhat.com/ml/gdb-testers/2002-q4/msg00010.html

    . gdb.threads/schedlock.exp: *

        This test script is useless in this release because of a
        signed-versus-unsigned bug.

	Daniel J has an obvious fix, which has been applied to gdb HEAD:

	  http://sources.redhat.com/ml/gdb-patches/2002-10/msg00454.html

  . HEAD

    checkout date is '2003-03-01 00:59:37 UTC'

    . gdb.c++/annota2.exp: annotate-quit

      Same analysis as 5.3.

    . gdb.c++/classes.exp: ptype class default_private_class
      gdb.c++/classes.exp: ptype struct default_public_struct
      gdb.c++/classes.exp: ptype struct explicit_public_struct
      gdb.c++/classes.exp: ptype struct mixed_protection_struct
      gdb.c++/classes.exp: ptype struct private_struct
      gdb.c++/classes.exp: ptype struct protected_struct
	XFAIL -> PASS

	David C improved the test script so that it accepts more
	output as legal.

    . gdb.c++/templates.exp: print Foo<volatile char *>::foo
	FAIL -> PASS
	FAIL -> KFAIL
      gdb.c++/templates.exp: print Foo<volatile char*>::foo
	null -> KFAIL
	null -> PASS
      gdb.c++/templates.exp: ptype Bar
      gdb.c++/templates.exp: ptype Baz
      gdb.c++/templates.exp: ptype Foo
      gdb.c++/templates.exp: ptype Qux
      gdb.c++/templates.exp: ptype Spec
	XFAIL -> KFAIL
	XFAIL -> PASS

	David C improved the test script and added more tests.

    . gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily

	Same analysis as 5.3.

    . gdb.threads/schedlock.exp: *

	I'm tired this week, and so are the similes.

	This test is still in a state where it's better to analyze the
	absolute results than to compare results from date to date.

    . gdb.trace/packetlen.exp: setup collect actions

	Daniel J fixed a bug in gdb.

. Test Matrix

  target     => native
  host       => i686-pc-linux-gnu
  osversion  => red-hat-8.0
  gdb        => 5.3, HEAD%20030228
  gcc        => 2.95.3, 3.2-7-rh, 3.2.2, gcc-3_2-branch%20030227, gcc-3_3-branch%20030227, HEAD%20030227
  binutils   => 2.13.90.0.2-rh, 2.13.2.1, HEAD%20030227
  glibc      => 2.2.93-5-rh
  gformat    => dwarf-2, stabs+
  glevel     => 2
  count         64 = 1 * 1 * 1 * 2 * (5*3+1*1) * 1 * 2 * 1

  'target' and 'host' are gnu configuration triples.

  'osversion' is the host operating system name, which is additional
  information beyond 'host'.

  'gdb', 'gcc', 'binutils', and 'glibc' are version 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.
  cvs versions (head and branch) show the checkout date after a '%' delimiter.

  'gformat' is the debugging information format.
  'glevel' is the debugging level.

  'count' is the total number of configurations tested.
  The vendor gcc is available only with vendor binutils,
    thus the '(5*3+1*1)' term for gcc/binutils combinations.

. Baseline software

  . host=i686-pc-linux-gnu, osversion=red-hat-8.0

    make 3.79.1
    binutils 2.13.2.1
    gcc 3.2.2
    flex 2.5.4
    bison 1.875
    tcl 8.4.1
    expect 5.38.0
    dejagnu 1.4.3

    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 they are licensed under the GPL.

      ftp://ftp.shout.net/pub/users/mec/migchain/migchain-0.3.tar.gz

. Test Bed Changes Since Last Report

  None.


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