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]

gdb, native i686-pc-linux-gnu


. Highlights of This Spin

  No new bugs detected.

  I added gcc 3.3.5-20040914.  It's healthy.

  My current tables are always at

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

. Gdb Regression Summary

  gdb drow_intercu-20040221-branch versus gdb HEAD
    not analyzed

  gdb HEAD versus gdb gdb_6_2-branch
    no regressions

  gdb gdb_6_2-branch versus gdb 6.2.1
    no improvements and no regressions

. Gcc Regression Summary

  gcc HEAD versus gcc 3.4.2
    gcc/13974
    gdb/1656 gdb/1734 gdb/1742

  gcc gcc-3_4-branch versus gcc 3.4.2
    no improvements and no regressions

  gcc 3.4.2 versus gcc 3.3.4
    gcc/12267 gcc/13708
    gdb/1537 gdb/1540

  gcc gcc-3_3-branch versus gcc 3.3.4
  gcc 3.3.5-20040914 versus gcc 3.3.4
    no improvements and no regressions

  gcc 3.3.4 versus gcc 2.95.3
    not analyzed

. Binutils Regression Summary

  binutils HEAD versus binutils 2.15
    no improvements and no regressions

. Old Bugs Fixed Since Last Spin

  . gcc HEAD

    http://sources.redhat.com/gdb/bugs/1743
    gdb.threads/*.c does not compile with gcc HEAD 20040806

      Michael Chastain fixed a bug in the gdb test suite.

. New Bugs Detected Since Last Spin

  None.

. PR Count

  Query executed 2004-09-22 04:28:38 UTC

  1782 matches found
    22 analyzed
   841 closed
    24 feedback
   875 open
     3 paperwork
    17 suspended
  1782 TOTAL

. Libiberty Testing

  . target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
      binutils HEAD                     746 tests, 0 failures
      gcc gcc-3_3-branch                649 tests, 0 failures
      gcc gcc-3_4-branch                745 tests, 0 failures
      gcc HEAD                          746 tests, 0 failures
      gdb HEAD                          746 tests, 0 failures
      gdb drow_intercu-20040221-branch  745 tests, 0 failures
      gdb gdb_6_2-branch                746 tests, 0 failures

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

. Gdb Testing

  My tables are at

    http://www.shout.net/~mec/sunday/2004-09-15/index.html

  The previous tables are at

    http://www.shout.net/~mec/sunday/2004-09-08/index.html

  . Non-Pass Results

    suite 6.2.1
      suite 6.2.1                         1480 non-PASS results
      suite HEAD                           376 non-PASS results
    gdb gdb_6_2-branch
      suite gdb_6_2-branch                1481 non-PASS results
      suite HEAD                           377 non-PASS results
    gdb HEAD
      suite HEAD                           373 non-PASS results
    gdb drow_intercu-20040221-branch
      suite drow_intercu-20040221-branch  1507 non-PASS results
      suite HEAD                           396 non-PASS results

  . gdb 6.2.1

    . suite 6.2.1

      . gdb.base/constvars.exp: ptype crass
        gdb.base/constvars.exp: ptype qux1
        gdb.base/volatile.exp: ptype qux2
          XFAIL -> FAIL

          This happened with gcc HEAD -gstabs+.

          gcc HEAD changed its version number from gcc 3.5.0 to gcc
          4.0.0.  A few gdb tests are sensitive to the major version
          number of gcc.  The output of gdb did not change, but these
          three tests need an update.

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

          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.threads/manythreads.exp: GDB exits after stopping multithreaded program
        gdb.threads/manythreads.exp: stop threads 1
        gdb.threads/manythreads.exp: stop threads 2
          PASS -> FAIL
          FAIL -> PASS
          FAIL -> FAIL

          This is a bug in gdb.  It happens intermittently.

            http://sources.redhat.com/gdb/bugs/1650
            manythreads.exp

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

          Fluctuation with unknown cause.  Probably harmless.

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

                   t0  t1  t2  t3  t4  t5
            PASS    1  26  26  26  25  26
            FAIL   25   0   0   0   1   0

  . gdb 6.2.1

    . suite HEAD

      . gdb.base/constvars.exp: ptype crass
        gdb.base/constvars.exp: ptype qux1
        gdb.base/volatile.exp: ptype qux2
          XFAIL -> FAIL

          Same analysis as gdb 6.2.1 suite 6.2.1.

      . gdb.base/define.exp: *
          blank -> PASS
          blank -> FAIL

          Jason Molenda wrote a new test script.

      . gdb.base/signals.exp: *
          PASS -> blank
          KFAIL -> blank
          XFAIL -> blank

          Andrew Cagney deleted some redundant tests.

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

          Same analysis as gdb 6.2.1 suite 6.2.1.

      . gdb.threads/gcore-thread.exp: *
        gdb.threads/killed.exp: *
        gdb.threads/pthreads.exp: *
          UNSUPPORTED -> blank
          blank -> PASS

          This happened with gcc HEAD.

          Michael Chastain fixed the test programs.

            http://sources.redhat.com/gdb/bugs/1743
            gdb.threads/*.c does not compile with gcc HEAD 20040806

      . gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
        gdb.threads/manythreads.exp: stop threads 1
        gdb.threads/manythreads.exp: stop threads 2
          PASS -> FAIL
          FAIL -> PASS

          Same analysis as gdb 6.2.1 suite 6.2.1.

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

                   t0  t1  t2  t3  t4  t5
            PASS    2  12  13  13  14  14
            FAIL   12   2   1   1   0   0

  . gdb gdb_6_2-branch

    . suite gdb_6_2-branch

      . gdb.base/constvars.exp: ptype crass
        gdb.base/constvars.exp: ptype qux1
        gdb.base/volatile.exp: ptype qux2
          XFAIL -> FAIL

          Same analysis as gdb 6.2.1 suite 6.2.1.

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

          Same analysis as gdb 6.2.1 suite 6.2.1.

      . gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
        gdb.threads/manythreads.exp: stop threads 1
        gdb.threads/manythreads.exp: stop threads 2
          PASS -> FAIL
          FAIL -> PASS
          FAIL -> FAIL

          Same analysis as gdb 6.2.1 suite 6.2.1.

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

          Same analysis as gdb 6.2.1 suite 6.2.1.

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

                   t0  t1  t2  t3  t4  t5
            PASS    1  26  26  25  25  26
            FAIL   25   0   0   1   1   0

  . gdb gdb_6_2-branch

    . suite HEAD

      . gdb.base/constvars.exp: ptype crass
        gdb.base/constvars.exp: ptype qux1
        gdb.base/volatile.exp: ptype qux2
          XFAIL -> FAIL

          Same analysis as gdb 6.2.1 suite 6.2.1.

      . gdb.base/define.exp: *
        gdb.base/signals.exp: *
        gdb.threads/gcore-thread.exp: *
        gdb.threads/killed.exp: *
        gdb.threads/pthreads.exp: *
          * -> *

          Same analyses as gdb 6.2.1 suite HEAD.

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

          Same analysis as gdb 6.2.1 suite 6.2.1.

      . gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
        gdb.threads/manythreads.exp: stop threads 1
        gdb.threads/manythreads.exp: stop threads 2
          PASS -> FAIL
          FAIL -> PASS
          FAIL -> FAIL

          Same analysis as gdb 6.2.1 suite 6.2.1.

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

                   t0  t1  t2  t3  t4  t5
            PASS    5   9  12  13  14  14
            FAIL    9   5   2   1   0   0

  . gdb HEAD

    . suite HEAD

      . gdb.base/constvars.exp: ptype crass
        gdb.base/constvars.exp: ptype qux1
        gdb.base/volatile.exp: ptype qux2
          XFAIL -> FAIL

          Same analysis as gdb 6.2.1 suite 6.2.1.

      . gdb.base/define.exp: *
        gdb.base/signals.exp: *
        gdb.threads/gcore-thread.exp: *
        gdb.threads/killed.exp: *
        gdb.threads/pthreads.exp: *
          * -> *

          Same analyses as gdb 6.2.1 suite HEAD.

      . gdb.threads/manythreads.exp: GDB exits after stopping multithreaded program
        gdb.threads/manythreads.exp: stop threads 1
        gdb.threads/manythreads.exp: stop threads 2
          PASS -> FAIL
          FAIL -> PASS
          FAIL -> FAIL

          Same analysis as gdb 6.2.1 suite 6.2.1.

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

          Same analysis as gdb 6.2.1 suite 6.2.1.

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

                   t0  t1  t2  t3  t4  t5
            PASS    5  25  27  27  30  30
            FAIL   25   5   3   3   0   0

  . gdb drow_intercu-20040221-branch

    The last change on this branch was 2004-08-07.

    . suite drow_intercu-20040221-branch

      I examined the tables and found nothing noteworthy.

    . suite HEAD

      I examined the tables and found nothing noteworthy.

. Package Versions

  . This Spin

    binutils  HEAD                          2004-09-14 11:17:30 UTC
    gcc       HEAD                          2004-09-14 11:36:41 UTC
    gcc       gcc-3_4-branch                2004-09-14 11:52:23 UTC
    gcc       gcc-3_3-branch                2004-09-14 12:08:22 UTC
    gdb       HEAD                          2004-09-15 17:18:53 UTC
    gdb       drow_intercu-20040221-branch  2004-09-15 17:30:48 UTC
    gdb       gdb_6_2-branch                2004-09-15 17:36:49 UTC

  . Last Spin

    binutils  HEAD                          2004-09-05 20:07:10 UTC
    gcc       HEAD                          2004-09-07 13:50:37 UTC
    gcc       gcc-3_4-branch                2004-09-05 22:49:01 UTC
    gcc       gcc-3_3-branch                2004-09-05 23:04:55 UTC
    gdb       HEAD                          2004-09-08 14:39:40 UTC
    gdb       drow_intercu-20040221-branch  2004-09-08 14:52:53 UTC
    gdb       gdb_6_2-branch                2004-09-08 14:59:19 UTC

. Test Matrix

  target     => native
  host       => i686-pc-linux-gnu
  osversion  => red-hat-8.0
  dejagnu    => dejagnu 1.4.4
  expect     => expect 5.41
  tcl        => tcl 8.4.6
  gdb        => 6.2.1, gdb_6_2-branch, HEAD, drow_intercu-20040221-branch
  suite      => 6.2.1, gdb_6_2-branch, HEAD, drow_intercu-20040221-branch
  cc         => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.4, gcc 3.3.5-20040914, gcc gcc-3_3-branch, gcc 3.4.2, gcc gcc-3_4-branch, gcc HEAD
  as         => binutils 2.13.90.0.2-rh, binutils 2.15, binutils HEAD
  ld         => binutils 2.13.90.0.2-rh, binutils 2.15, binutils HEAD
  libc       => glibc 2.2.93-5-rh
  gformat    => dwarf-2, stabs+
  glevel     => 2
  count      => 146

  '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 tested gdb 6.2.1 suite 6.2.1, gdb gdb_6_2-branch suite
  gdb_6-2-branch, and gdb HEAD suite HEAD with the full spectrum of as
  and ld.  I tested other gdb/suite configurations only with as binutils
  2.15 + ld binutils 2.15.

. Test Bed Changes Since Last Report

  I dropped gdb 6.2 and gdb 6.2.0.90.

  I dropped gcc 3.4.1, gcc 3.4.2-20040829, and gcc 3.4.2-20040902.

  I added gcc 3.3.5-20040914.


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