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 test results, gdb, 2002-04-04


On the 5.2 branch:

  pr's gdb/379 and gdb/380 were fixed (already fixed in HEAD).

On gdb HEAD:

  pr gdb/381 was fixed (but is still open in 5.2 branch).

  configuration gcc 2.95.3 -gdwarf-2 improved a lot,
  but there is a minor regression.  pr gdb/460.
  
  There is a new test script, gdb.base/relocate.exp.
  It reveals a gdb bug with gcc=vendor (2.96-rh).  pr gdb/461.

Michael C

. Summary

  . Test Matrix

    . Matrix

      target:   native
      host:     i686-pc-linux-gnulibc2.2%rh-7.2
      gdb:      5.1.1, gdb_5_2-branch%20020404, HEAD%20020404
      gcc:      2.95.3, vendor, 3.0.4, gcc-3_1-branch%20020404, HEAD%20020404
      glibc:    vendor
      goption:  -gdwarf-2, -stabs+
      count:    30=1*1*3*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 "vendor" are the vendor-supplied facility.
      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-04/index.html

    . Overview

      gdb 5.1.1:           0 build aborts, 0 test aborts, 400 attention lines
      gdb gdb_5_2-branch:  0 build aborts, 0 test aborts, 275 attention lines
      gdb HEAD:            0 build aborts, 0 test aborts,  86 attention lines

      an attention line is:
        error warning fail kfail unresolved untested unsupported
      an attention line is not:
        pass xpass xfail

    . Old bugs fixed

      http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=379
      Regression: The step command does not stop in the right place.
      Fixed in 5.2 branch (was already fixed in HEAD)

      http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=380
      Regression: "No line number known for main." and many other functions.
      Fixed in 5.2 branch (was already fixed in HEAD)

      http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=381
      Regression: src_and_asm_line line attribute "line" for file gdb.mi/basics.c changed from 31 to 0 in several places.
      Fixed in HEAD (still open in 5.2 branch).

    . New bugs detected

      http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=460
      Regression: gdb prints extraneous address at breakpoint.
      This is a regression in HEAD.

      http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=461
      gdb.base/relocate.exp fails with gcc 2.96-rh.
      This is a new test in HEAD.

. Test protocol changes since last report

  I tweaked the html output.  It's about 20% shorter now.

. 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

    I tried binutils 2.12, but it caused additional FAILs.
    I need to analyze this.  Meanwhile, I am staying with binutils 2.11.2.

. 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-03-31.

      http://www.shout.net/~mec/sunday/2002-03-31/Analysis.txt

    Configuration numbers for the difference grids are in:

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

    Difference grid key:

      +  gdb improved
      -  gdb 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

      No significant changes.

    . gdb_5_2-branch

      . Difference Grid

        gdb.base/break.exp                  +11
        gdb.base/call-ar-st.exp             +11
        gdb.base/callfuncs.exp              +11
        gdb.base/display.exp                +11
        gdb.base/ending-run.exp             +11
        gdb.base/funcargs.exp               +11
        gdb.base/list.exp                   +11
        gdb.base/ptype.exp                  +11
        gdb.base/shlib-call.exp             +11
        gdb.base/step-line.exp              +11
        gdb.base/step-test.exp              +11
        gdb.base/structs2.exp               +11
        gdb.c++/method.exp                  +11
        gdb.c++/namespace.exp               +11
        gdb.c++/overload.exp                +11
        gdb.c++/ovldbreak.exp               +11
        gdb.mi/mi-disassemble.exp           +11
        gdb.mi/mi-simplerun.exp             +11
        gdb.mi/mi-var-display.exp           +11
        gdb.mi/mi0-disassemble.exp          +11
        gdb.mi/mi0-simplerun.exp            +11
        gdb.mi/mi0-var-display.exp          +11
        gdb.trace/tracecmd.exp              +11

      . Gdb Improved

        pr gdb/379 and pr gdb/380 were fixed in the branch.
        They were already fixed in HEAD.

    . HEAD

      . Difference Grid
                                        .20 .21 .22 .23 .24 .25 .26 .27 .28 .29
        gdb.base/break.exp              +20
        gdb.base/call-ar-st.exp         +20
        gdb.base/callfuncs.exp          +20
        gdb.base/condbreak.exp          -20
        gdb.base/ena-dis-br.exp         -20
        gdb.base/ending-run.exp         +20
        gdb.base/funcargs.exp           +20
        gdb.base/list.exp               +20
        gdb.base/relocate.exp           *20 *21 _22 _23 *24 *25 *26 *27 *28 *29
        gdb.base/step-line.exp          +20
        gdb.base/step-test.exp          +20
        gdb.base/structs2.exp           +20
        gdb.c++/annota2.exp                     ,22                 ,27
        gdb.c++/classes.exp             @20 @21
        gdb.c++/method.exp              +20
        gdb.c++/namespace.exp           +20
        gdb.mi/mi-disassemble.exp       +20                         +27     +29
        gdb.mi/mi-var-display.exp       +20
        gdb.mi/mi0-disassemble.exp      +20                         +27     +29
        gdb.mi/mi0-var-display.exp      +20
        gdb.trace/tracecmd.exp          +20

      . Gdb Improved

        gdb improved its handling of line numbers for gcc 2.95.3 -gdwarf-2,
        causing many test improvements.

        . gdb.mi/disassemble.exp: data-disassemble file, line, number (zero lines) assembly mixed

          pr gdb/381 was fixed in HEAD (but is still open for 5.2 branch).

      . Gdb Regressed

        . 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

          In some cases, gdb regressed in its handling of line numbers.
          The bug is not serious but it is a bug.  pr gdb/460.

      . Test Suite Improved

        . gdb.c++/classes.exp: calling method for small class

          The test suite changed to accommodate a gdb message change
          from 2001-12.

      . New Test With Good Result

        . gdb.base/relocate.exp

          This is a new test script.  Most tests PASS in most configurations.

      . New Test With Bad Result

        . gdb.base/relocate.exp: get address of function_bar (unknown output)

          This test fails with gcc=vendor (2.96-rh).  It prints a symbol
          from the wrong section.  pr gdb/461.

      . 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]