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 report, gdb, 2002-04-21


No regressions this week!

gcc improved their 3.1 branch and HEAD, which improved some test suite
results in all vesions of gdb (including gdb 5.1.1).  I did a test run on
2002-04-18 which showed some regressions relative to 2002-04-11.  But the
test run of 2002-04-21 showed no regressions relative to 2002-04-11.
Very nice.

I added gdb 5.1.91 to the test matrix.  I compared to gdb 5.1.1 and
found no gdb regressions.

Michael C

. Summary

  . Test Matrix

    . Matrix

      target:   native
      host:     i686-pc-linux-gnulibc2.2%rh-7.2
      gdb:      5.1.1, 5.1.91, gdb_5_2-branch%20020421, HEAD%20020421
      gcc:      2.95.3, 2.96-rh, 3.0.4, gcc-3_1-branch%20020421, HEAD%20020421
      glibc:    vendor
      goption:  -gdwarf-2, -gstabs+
      count:    40 = *(1 1 4 5 1 2)

    . Notes

      target and host names are gnu triples with extra information after
      a '%' delimiter.

      versions which start with a number are official releases or snapshots.
      versions named "HEAD" are the cvs HEAD.
      versions with any other name are cvs branches.
      cvs versions show the pull date after a '%' delimiter.

      gcc releases and snapshots are built with binutils 2.11.2

      gcc cvs versions are built with binutils HEAD with the same pull date.

    . libiberty

      All tests passed.

    . gdb

      . Tables

	. http://www.shout.net/~mec/sunday/2002-04-22/index.html

      . Overview

	gdb 5.1.1:           0 build aborts, 0 test aborts, 636 attention lines
	gdb 5.1.91:          0 build aborts, 0 test aborts, 457 attention lines
	gdb gdb_5_2-branch:  0 build aborts, 0 test aborts, 457 attention lines
	gdb HEAD:            0 build aborts, 0 test aborts, 268 attention lines

	An attention line is a line with one or more attention results.

	An attention result is any result except PASS.  This includes
	ERROR, WARNING, FAIL, KPASS, KFAIL, XPASS, XFAIL, UNRESOLVED,
	UNTESTED, SUPPORTED, and unknown results.

      . Old bugs fixed

	None.

      . New bugs detected

	None.

. Test protocol changes since last report.

  I added gdb 5.1.91.

. Baseline software

  . host i686-pc-linux-gnu%rh-7.2

    make 3.79.1
    binutils 2.11.2
    gcc 3.0.4
    flex 2.5.4
    bison 1.33
    tcl 8.3.4
    expect 4.33.0
    dejagnu 1.4.2 + FernandoN kfail patch.

. Analysis

  . libiberty

    . results

      . target native

	. host i686-pc-linux-gnu%rh-7.2

          binutils HEAD                         All 648 tests passed
          gcc gcc-3_1-branch                    All 648 tests passed
          gcc HEAD                              All 648 tests passed
          gdb gdb_5_2-branch                    All 648 tests passed
          gdb HEAD                              All 648 tests passed

  . gdb

    The last report was 2002-04-11.

      http://www.shout.net/~mec/sunday/2002-04-11/Analysis.txt

    Configuration numbers for the difference grids are in:

      http://www.shout.net/~mec/sunday/2002-04-21/Differences-compare-by-date-two.html

    Difference grid key:

      +  gdb improved
      -  gdb regressed
      $  gcc improved
      =  gcc regressed
      @  test suite improved
      ~  test suite regressed
      *  new test with good result
      _  new test with bad result
      ,  noise: result changed but gdb behavior did not

    . 5.1.1

      . Difference Grid

	gdb.base/condbreak.exp                                  $06     $08
	gdb.base/ena-dis-br.exp					$06     $08
	gdb.base/funcargs.exp        				$06     $08
	gdb.base/interrupt.exp		        ,02
	gdb.c++/annota2.exp		        ,02
	gdb.c++/ovldbreak.exp					$06     $08

	. Gcc Improved

	  gdb.base/condbreak.exp: run until breakpoint at marker1
	  gdb.base/condbreak.exp: run until breakpoint at marker2
	  gdb.base/ena-dis-br.exp: continue to auto-disabled break marker2
	  gdb.base/ena-dis-br.exp: continue to break marker1
	  gdb.base/ena-dis-br.exp: continue to break marker1, 2nd time
	  gdb.base/funcargs.exp: print st
	  gdb.base/funcargs.exp: run to call5a
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : char
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : double
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : short
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : signed char
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : unsigned char
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : unsigned short

	    These test results improved for configurations gdb 5.1.1
	    gcc gcc-3_1-branch -gdwarf-2 and gdb 5.1.1 gcc HEAD -gdwarf-2.
	    gdb 5.1.1 stayed the same (same installation tree), and gcc
	    changed (10 days of CVS commits), so the improvement is in gcc.

	. Noise

	  . gdb.base/interrupt.exp: continue

	    This test appears to have a race condition between gdb input
	    and a SIGILL in the program under test.

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

	    This test is unstable.

    . 5.1.91

      This is the first report for 5.1.91.
      I compared gdb 5.1.1 versus gdb 5.1.91 and found no regressions.

    . gdb_5_2-branch

      . Difference Grid

					,10 ,11 ,12 ,13 ,14 ,15 ,16 ,17 ,18 ,19
	gdb.base/condbreak.exp                                  $16     $18
	gdb.base/ena-dis-br.exp					$16     $18
	gdb.base/funcargs.exp        				$16     $18
	gdb.c++/annota2.exp		        ,12     ,14         ,17
	gdb.c++/ovldbreak.exp					$16     $18

	. Gcc Improved

	  gdb.base/condbreak.exp: run until breakpoint at marker1
	  gdb.base/condbreak.exp: run until breakpoint at marker2
	  gdb.base/ena-dis-br.exp: continue to auto-disabled break marker2
	  gdb.base/ena-dis-br.exp: continue to break marker1
	  gdb.base/ena-dis-br.exp: continue to break marker1, 2nd time
	  gdb.base/funcargs.exp: print st
	  gdb.base/funcargs.exp: run to call5a
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : char
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : double
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : short
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : signed char
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : unsigned char
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : unsigned short

	    These test results improved for configurations gdb gdb_5_2-branch
	    gcc gcc-3_1-branch -gdwarf-2 and gdb gdb_5_2-branch gcc HEAD
	    -gdwarf-2.  gdb 5.1.1 showed the same improvements, so I believe
	    this is an improvement in gcc.

	. Noise

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

	    This test is unstable.

    . HEAD

      . Difference Grid

	gdb.base/condbreak.exp                                  $26     $28
	gdb.base/ena-dis-br.exp					$26     $28
	gdb.base/funcargs.exp        				$26     $28
	gdb.c++/annota2.exp		                ,24
	gdb.c++/ovldbreak.exp					$26     $28

	. Gcc Improved

	  gdb.base/condbreak.exp: run until breakpoint at marker1
	  gdb.base/condbreak.exp: run until breakpoint at marker2
	  gdb.base/ena-dis-br.exp: continue to auto-disabled break marker2
	  gdb.base/ena-dis-br.exp: continue to break marker1
	  gdb.base/ena-dis-br.exp: continue to break marker1, 2nd time
	  gdb.base/funcargs.exp: print st
	  gdb.base/funcargs.exp: run to call5a
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : char
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : double
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : short
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : signed char
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : unsigned char
	  gdb.c++/ovldbreak.exp: continue to bp overloaded : unsigned short

	    These test results improved for configurations gdb HEAD
	    gcc gcc-3_1-branch -gdwarf-2 and gdb HEAD gcc HEAD -gdwarf-2.
	    gdb 5.1.1 showed the same improvements, so I believe this is
	    an improvement in gcc.

	. Noise

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

	    This test is unstable.


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