This is the mail archive of the gcc-testresults@gcc.gnu.org mailing list for the GCC 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-09


Highlights of this report:

. The CLI has a regression with ^Z (pr gdb/1046).

. I added gcc 3.2.2.  I saw no regressions in gdb test results from gcc
  3.2.1 to gcc 3.2.2.  I dropped gcc-3_2-branch and gcc-3.2.2-20030203.
  Next report, I will drop gcc 3.2.1.

. This will be the last report to cover gdb gdb_5_3-branch, unless I hear
  that there is likely to be another release from this branch, or that
  someone has an interest in continued coverage, 

. gcc gcc-3_3-branch and gcc HEAD have many -gstabs+ regressions
  compared to gcc 3.2.2.  This is PR gdb/1026.

    pr gdb/1026: regression in casts.exp from gcc 3.2.1 to gcc gcc-3_3-branch%20030128
    http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=10NN

. the pesky annotate-quit bug appears to be fixed (pr gdb/544).

My tables are here:

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

Michael C

. Old Bugs Fixed

  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

    This was an intermittent failure when sending ^C to gdb.
    The bug has not happened since the big interpreter merge.

. New Bugs Detected

  pr gdb/1046: regression: ^Z (suspend) no longer works
  http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=1046

    This started happening with the big interpreter merge.
    Mark K wrote some analysis.

. PR count

  Query executed 2003-02-10T07:18:43Z

  1046 matches found
    16 analyzed
   426 closed
    10 feedback
   586 open
     8 suspended

. 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.1, binutils HEAD                  All 648 tests passed
      gcc 3.2.2, binutils HEAD                  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 gdb_5_3-branch                        All 649 tests passed
      gdb HEAD                                  649 tests, 0 failures

. Gdb Testing

  My tables are at:

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

  The previous report was 2003-02-05:

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

  . Counts

    gdb 5.3:             0 build aborts, 0 test aborts, 385 non-PASS results
    gdb gdb_5_3_branch:  0 build aborts, 0 test aborts, 383 non-PASS results
    gdb HEAD:            0 build aborts, 0 test aborts, 322 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 from unknown cause.

    . 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

  . gdb_5_3-branch

    checkout date is '2003-02-09 18:19:53 UTC'

    . gdb.c++/annota2.exp: annotate-quit
      gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
      gdb.threads/schedlock.exp: *

	Same analysis as 5.3.

  . HEAD

    checkout date is '2003-02-09 18:18:02 UTC'

    . gdb.base/setshow.exp: set radix 11
      gdb.base/setshow.exp: set radix 16
      gdb.base/setshow.exp: show radix {16}
	PASS -> FAIL
	  gcc HEAD, binutils HEAD, libc vendor, gformat stabs+

	  The test script de-synchronized just before this in some
	  tests that change the prompt.  Gdb's responses are okay.

	  Here is a log excerpt:

	    (gdb) PASS: gdb.base/setshow.exp: show listsize (100)
	    set prompt (FooBarBaz) PASS: gdb.base/setshow.exp: set prompt (FooBarBaz)
	    
	    (FooBarBaz) show prompt
	    Gdb's prompt is "(FooBarBaz) ".
	    (FooBarBaz) PASS: gdb.base/setshow.exp: show prompt (FooBarBaz)
	    set prompt (gdb) PASS: gdb.base/setshow.exp: set prompt (gdb)
	    
	    (gdb) FAIL: gdb.base/setshow.exp: set radix 11
	    set radix 11
	    Unsupported output radix ``decimal 11''; output radix unchanged.
	    (gdb) FAIL: gdb.base/setshow.exp: set radix 16
	    set radix 16
	    Input and output radices now set to decimal 16, hex 10, octal 20.
	    (gdb) FAIL: gdb.base/setshow.exp: show radix (16)
	    show radix
	    Input and output radices set to decimal 16, hex 10, octal 20.
	    (gdb) set radix
	    Input and output radices now set to decimal 10, hex a, octal 12.
	    (gdb) PASS: gdb.base/setshow.exp: set radix 10

	  The first 'set prompt (FooBarBaz)' matched on the echo'ed input,
	  presumably because 'expect' had an incomplete output segment
	  and the test is poorly written.  The new command interpreter
	  may have perturbed the input/output segments seen by 'expect'.

	  I am going to let this slide until it happens a second time.

      . gdb.c++/annota2.exp: annotate-quit
	  KFAIL -> PASS

	  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

	  Jim I, Keith S, Elena Z, and Andrew C committed a new command
	  interpreter.  This long-standing bug appears to be fixed!

      . gdb.c++/local.exp: Local out of scope
	  FAIL -> KFAIL

	  pr gdb/825: gdb gets scope of class local to a function wrong
	  http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=825
	  Michael C improved a FAIL to a KFAIL.

      . gdb.mi/mi-cli.exp: *
	  null -> PASS

	  Keith S and Andrew C wrote a new test script.
	  All tests PASSed in all configurations.

      . gdb.mi/mi-syn-frame.exp: *
	  FAIL -> PASS

	  Jason M fixed the test script.
	  All tests PASSed in all configurations.

      . gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
	  Same analysis as 5.3.

      . gdb.threads/schedlock.exp: *

	These results have more complications than a Najdorf Sicilian.

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

  . Test Matrix

    target     => native
    host       => i686-pc-linux-gnu
    osversion  => red-hat-8.0
    gdb        => 5.3, gdb_5_3-branch%20030209, HEAD%20030209
    gcc        => 2.95.3, 3.2-7-rh, 3.2.1, 3.2.2, gcc-3_3-branch%20030209, HEAD%20030209
    binutils   => 2.13.90.0.2-rh, 2.13.2.1, HEAD%20030209
    libc       => 2.2.93-5-rh
    gformat    => dwarf-2, stabs+
    count         96 = 1 * 1 * 1 * 3 * (5*3+1*1) * 1 * 2

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

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

    'gdb', 'gcc', 'binutils', and 'libc' 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.

    '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.1
      flex 2.5.4
      bison 1.35
      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

    I added gcc 3.2.2.
    I dropped gcc 3.2.2-20030203.
    I dropped gcc gcc-3_2_2-branch.
    Next report, I plan to drop gcc 3.2.1.

    I changed the table formatting so that 'kpass', 'kfail', 'xpass', and
    'xfail' are italic.  The only result in plain text is 'pass'.


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