gdb, native i686-pc-linux-gnu

Michael Elizabeth Chastain mec.gnu@mindspring.com
Fri Feb 13 15:16:00 GMT 2004


. Highlights of This Spin

  I added gcc 3.3.3-20040210.  This version of gcc is healthy.

  gcc HEAD generates dwarf-2 location lists now.  gcc HEAD -gdwarf2
  generates them explicitly, naturally; and gcc HEAD -gstabs+ picks up
  dwarf-2 debug info from the language run-time libraries for C++, Java,
  or Objective-C.  gdb 6.0 crashes when it encounters one of these
  location lists.  gdb HEAD works fine.  So do gdb
  carlton_dictionary-branch and gdb drow-cplus-branch.

  The current tables are always at

    http://www.shout.net/~mec/sunday/current/index.html

. Gdb Regression Summary

  gdb HEAD versus gdb 6.0
    gdb/826 gdb/931 gdb/1505 gdb/1512 gdb/1516

. Gcc Regression Summary

  gcc 3.3.3-20040131 versus gcc 3.3.2
  gcc 3.3.3-20040210 versus gcc 3.3.2
  gcc gcc-3_3-branch versus gcc 3.3.2
    No significant differences; no improvements or regressions.

  gcc gcc-3_4-branch versus gcc 3.3.2
    gcc/12267 gcc/13708 gcc/13956 gcc/13974
    gdb/1537 gdb/1540
    classes.exp unanalyzed regressions

  gcc HEAD versus gcc 3.3.2
    gcc/12267 gcc/13708 gcc/13956 gcc/13974
    gdb/1537 gdb/1540
    classes.exp unanalyzed regressions

  gcc tree-ssa-20020619-branch versus gcc HEAD
    gcc/14048 gcc/14049

. Old Bugs Fixed

  None.

. New Bugs Detected

  None.

. PR Count

  Query executed 2004-02-13 11:41:24 UTC

  1552 matches found
    22 analyzed
   718 closed
    25 feedback
   768 open
     3 paperwork
    16 suspended
  1552 TOTAL

. Libiberty Testing

  . target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
      binutils HEAD                  742 tests, 0 failures
      gcc gcc-3_3-branch             649 tests, 0 failures
      gcc gcc-3_4-branch             742 tests, 0 failures
      gcc HEAD                       742 tests, 0 failures
      gcc tree-ssa-20020619-branch   742 tests, 0 failures
      gdb HEAD                       742 tests, 0 failures
      gdb carlton_dictionary-branch  742 tests, 0 failures
      gdb drow-cplus-branch          742 tests, 0 failures

    For gcc tests, the test results are with binutils 2.14.
    The binutils version should not make a difference.

. Gdb Testing

  My tables are at

    http://www.shout.net/~mec/sunday/2004-02-11/index.html

  The previous tables are at

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

  . Non-Pass Results

    gdb 6.0
      suite 6.0                         456 non-PASS results
      suite HEAD                        649 non-PASS results
    gdb HEAD
      suite HEAD                        481 non-PASS results
    gdb carlton_dictionary-branch
      suite carlton_dictionary-branch   480 non-PASS results
      suite HEAD                        491 non-PASS results
    gdb drow-cplus-branch
      suite drow-cplus-branch           613 non-PASS results
      suite HEAD                        614 non-PASS results

    I run each version of gdb with two test suites: the test suite that
    comes with that version of gdb and the test suite that comes with
    gdb HEAD.

  . gdb 6.0

    . suite 6.0

      . gdb.base/break.exp: *
        gdb.cp/pr-1210.exp: *
        gdb.cp/userdef.exp: *
        gdb.java/jmisc1.exp: *
        gdb.java/jmisc2.exp: *
        gdb.objc/basicclass.exp: *
          blank -> ERROR
          PASS -> FAIL
          PASS -> UNRESOLVED
          FAIL -> blank

          This happened with gcc HEAD -gdwarf-2 and gcc HEAD -gstabs+.

          gcc HEAD generates dwarf-2 location lists.
          gdb 6.0 crashes when it encounters a dwarf-2 location list.

          Even when I compile the test program with gcc HEAD -gstabs+,
          the run-time libraries for C++, Java, and Objective-C have
          their own debugging symbols.  These symbols are in dwarf-2
          format.

      . gdb.cp/annota2.exp: annotate-quit
          PASS -> KFAIL
        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.mi/mi*-pthreads.exp: check mi_thread_command_set: -thread-select [3456]
          PASS -> blank
          blank -> PASS

          When gdb operates on an inferior program with threads, gdb uses
          hidden breakpoints in the thread library to track events such as
          thread creation and thread destruction.

          This causes some programs to behave differently because they
          aren't prepared to handle the additional signals caused by the
          hidden breakpoints.  The test program for mi*-pthreads.exp is
          such a program.

            http://sources.redhat.com/ml/gdb/2003-09/msg00279.html
            http://sources.redhat.com/gdb/bugs/259

      . gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
          PASS -> blank

          Fluctuation with unknown cause.  Probably harmless.

      . gdb.threads/schedlock.exp: *
          PASS
        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 configurations except for the
          "thread N ran" tests.  Here are the counts per thread.

                      PASS  FAIL
            thread 0     2    32
            thread 1    34     0
            thread 2    33     1
            thread 3    34     0
            thread 4    34     0
            thread 5    34     0

    . suite HEAD

      . gdb.base/break.exp: *
        gdb.cp/bs15503.exp: *
        gdb.cp/pr-1210.exp: *
        gdb.cp/userdef.exp: *
        gdb.java/jmisc1.exp: *
        gdb.java/jmisc2.exp: *
        gdb.objc/basicclass.exp: *
          blank -> ERROR
          blank -> FAIL
          blank -> UNRESOLVED
          PASS -> blank
          PASS -> FAIL
          PASS -> UNRESOLVED
          FAIL -> blank

          Same analysis as gdb 6.0 suite 6.0.

      . gdb.base/chng-syms.exp: running with invalidated bpt condition after executable changes
          blank -> PASS

          Fluctuation with unknown cause.

      . gdb.base/freebpcmd.exp: run program with breakpoint commands
          PASS -> KFAIL
          KFAIL -> KFAIL

          This is a non-deterministic memory corruption bug in gdb 6.0.
          It has been fixed in gdb HEAD.

            http://sources.redhat.com/gdb/bugs/1489
            GDB crashes executing breakpoint commands that continue the inferior

      . gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpoint)
          PASS -> blank

          Same analysis as gdb 6.0 suite 6.0.

      . gdb.threads/schedlock.exp: *
          PASS
        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 configurations except for the
          "thread N ran" tests.  Here are the counts per thread.

                      PASS  FAIL
            thread 0     2    32
            thread 1    33     1
            thread 2    34     0
            thread 3    34     0
            thread 4    34     0
            thread 5    34     0

  . gdb HEAD

    . suite HEAD

      . gdb.base/gdb1250.exp: setting breakpoint at abort
          PASS -> FAIL
        gdb.base/gdb1250.exp: running to abort in runto
          FAIL -> blank
        gdb.base/shlib-call.exp: setting breakpoint at shr1
          PASS -> FAIL

          These regressions happened with binutils HEAD.  This is more
          fallout from "make breakpoint pending on future shared library
          load?".  These are test script bugs.

      . gdb.threads/schedlock.exp: *
          PASS
        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 configurations except for the
          "thread N ran" tests.  Here are the counts per thread.

                      PASS  FAIL
            thread 0     5    29
            thread 1    27     7
            thread 2    34     0
            thread 3    34     0
            thread 4    34     0
            thread 5    34     0

  . gdb carlton_dictionary-branch

    . suite carlton_dictionary-branch

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

          Same analysis as gdb 6.0 suite 6.0.

      . gdb.threads/schedlock.exp: *
          PASS
        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 configurations except for the
          "thread N ran" tests.  Here are the counts per thread.

                      PASS  FAIL
            thread 0     4    12
            thread 1     7     9
            thread 2    12     4
            thread 3    13     3
            thread 4    15     1
            thread 5    16     0

    . suite HEAD

      . gdb.base/chng-syms.exp: running with invalidated bpt condition after executable changes
          PASS -> blank
          blank -> PASS

          Same analysis as gdb 6.0 suite HEAD.

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

          Same analysis as gdb 6.0 suite 6.0.

      . gdb.threads/print-threads.exp: Hit kill breakpoint, 10 (slow with kill breakpoint)
          PASS -> blank

          Same analysis as gdb 6.0 suite 6.0.

      . gdb.threads/schedlock.exp: *
          PASS
        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 configurations except for the
          "thread N ran" tests.  Here are the counts per thread.

                      PASS  FAIL
            thread 0     3    13
            thread 1    14     2
            thread 2    16     0
            thread 3    16     0
            thread 4    15     1
            thread 5    16     0

  . gdb drow-cplus-branch

    . suite drow-cplus-branch

      gdb.*/*: *
        * -> *

        Gdb and the test suite were merged from gdb HEAD.
        There were too many changes in test results to analyze.

    . suite HEAD

      gdb.*/*: *
        * -> *

        Gdb and the test suite were merged from gdb HEAD.
        There were too many changes in test results to analyze.

. Test Matrix

  target     => native
  host       => i686-pc-linux-gnu
  osversion  => red-hat-8.0
  dejagnu    => dejagnu 1.4.4
  expect     => expect 5.39
  tcl        => tcl 8.4.5
  gdb        => 6.0, HEAD, carlton_dictionary-branch, drow-cplus-branch
  suite      => 6.0, carlton_dictionary-branch, drow-cplus-branch, HEAD
  cc         => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.2, gcc 3.3.3-20040131, gcc 3.3.3-20040210, gcc gcc-3_3-branch, gcc gcc-3_4-branch, gcc HEAD, gcc tree-ssa-20020619-branch
  as         => binutils 2.13.90.0.2-rh, binutils 2.14, binutils HEAD
  ld         => binutils 2.13.90.0.2-rh, binutils 2.14, binutils HEAD
  libc       => glibc 2.2.93-5-rh
  gformat    => dwarf-2, stabs+
  glevel     => 2
  count      => 166

  '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 carlton_dictionary_branch and gdb drow-cplus-branch only
  with as/ld from binutils 2.14, not with vendor as/ld or binutils HEAD
  as/ld.  This means I do not test c_d-b and d-c-b with vendor gcc.

  I test each version gdb with its own gdb-test-suite and also with
  gdb-test-suite HEAD.

. Package Versions

  . This Spin

    binutils  HEAD                       2004-02-10 17:39:23 UTC
    gcc       tree-ssa-20020619-branch   2004-02-10 17:46:07 UTC
    gcc       HEAD                       2004-02-10 18:02:01 UTC
    gcc       gcc-3_4-branch             2004-02-10 18:14:15 UTC
    gcc       gcc-3_3-branch             2004-02-10 18:24:30 UTC
    gdb       HEAD                       2004-02-11 15:06:00 UTC
    gdb       carlton_dictionary-branch  2004-02-11 15:08:16 UTC
    gdb       drow-cplus-branch          2004-02-11 15:10:24 UTC

  . Last Spin

    binutils  HEAD                       2004-02-06 18:00:45 UTC
    gcc       tree-ssa-20020619-branch   2004-02-06 18:09:57 UTC
    gcc       HEAD                       2004-02-06 18:20:10 UTC
    gcc       gcc-3_4-branch             2004-02-06 18:29:34 UTC
    gcc       gcc-3_3-branch             2004-02-06 18:35:45 UTC
    gdb       HEAD                       2004-02-07 12:22:55 UTC
    gdb       carlton_dictionary-branch  2004-02-07 12:24:59 UTC
    gdb       drow-cplus-branch          2004-02-07 12:27:01 UTC

. Host Software

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

    make 3.79.1
    binutils 2.14
    gcc 3.3.2
    flex 2.5.4
    bison 1.875
    tcl 8.4.5
    expect 5.39
    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 added gcc 3.3.3-20040210.

  This is the last spin for gcc 3.3.3-20040131.

  Next spin will be the last spin for gdb carlton_dictionary-branch.



More information about the Gcc-testresults mailing list