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

  Nothing regressed since the last spin.

  I added gcc 3.4.2-20040902 and gcc 3.4.2.  There were no debug info
  regressions from gcc 3.4.1 to these versions.

  I added gdb 6.2.0.90 and gdb 6.2.1 (which have identical tarballs).
  There were no regressions versus gdb 6.2.

  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
  gdb 6.2.1 versus gdb 6.2
  gdb 6.2.0.90 versus gdb 6.2
    no regressions

. Gcc Regression Summary

  gcc HEAD versus gcc 3.4.1
    gcc/13974
    gdb/1656 gdb/1734 gdb/1742 gdb/1743

  gcc gcc-3_4-branch versus gcc 3.4.1
  gcc 3.4.2 versus gcc 3.4.1
  gcc 3.4.2-20040902 versus gcc 3.4.1
  gcc 3.4.2-20040829 versus gcc 3.4.1
    no regressions
    gcc/13956 has been fixed

  gcc 3.4.1 versus gcc 3.3.4
    gcc/12267 gcc/13708 gcc/13956
    gdb/1537 gdb/1540

  gcc gcc-3_3-branch 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

  None.

. New Bugs Detected Since Last Spin

  None.

. PR Count

  Query executed 2004-09-14 10:43:13 UTC

  1775 matches found
    22 analyzed
   839 closed
    24 feedback
   870 open
     3 paperwork
    17 suspended
  1775 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-08/index.html

  The previous tables are at

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

  . Non-Pass Results

    gdb 6.2
      suite 6.2                           1481 non-PASS results
      suite HEAD                           388 non-PASS results
    gdb 6.2.0.90
      suite 6.2.0.90                      1481 non-PASS results
      suite HEAD                           386 non-PASS results
    suite 6.2.1
      suite 6.2.1                         1482 non-PASS results
      suite HEAD                           384 non-PASS results
    gdb gdb_6_2-branch
      suite gdb_6_2-branch                1481 non-PASS results
      suite HEAD                           385 non-PASS results
    gdb HEAD
      suite HEAD                           384 non-PASS results
    gdb drow_intercu-20040221-branch
      suite drow_intercu-20040221-branch  1508 non-PASS results
      suite HEAD                           407 non-PASS results

  . gdb 6.2

    . suite 6.2

      . 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.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)
          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    0  34  34  34  34  34
            FAIL   34   0   0   0   0   0

  . gdb 6.2

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

      . 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    4  13  14  17  18  18
            FAIL   14   5   4   1   0   0

  . gdb 6.2.0.90

    This is the first spin for gdb 6.2.0.90.

    . suite 6.2.0.90

      Not analyzed.

    . suite HEAD

      I compared gdb 6.2 suite HEAD with gdb 6.2.0.90 suite HEAD.
      There were no regressions.

  . gdb 6.2.1

    This is the first spin for gdb 6.2.1.

    . suite 6.2.1

      Not analyzed.

    . suite HEAD

      I compared gdb 6.2 suite HEAD with gdb 6.2.1 suite HEAD.
      There were no regressions.

  . gdb gdb_6_2-branch

    . suite gdb_6_2-branch

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

          Same analysis as gdb 6.2 suite 6.2.

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

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

          Same analysis as gdb 6.2 suite 6.2.

      . 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    0  33  34  34  34  34
            FAIL   34   1   0   0   0   0

  . gdb gdb_6_2-branch

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

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

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

          Same analysis as gdb 6.2 suite 6.2.

      . 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    7  12  18  18  17  18
            FAIL   11   6   0   0   1   0

  . gdb HEAD

    . 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.2 suite 6.2.

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

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

          Same analysis as gdb 6.2 suite 6.2.

      . 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   15  23  33  35  36  38
            FAIL   23  15   5   3   2   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-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

  . Last Spin

    binutils  HEAD                          2004-08-31 16:00:38 UTC
    gcc       HEAD                          2004-08-31 16:33:12 UTC
    gcc       gcc-3_4-branch                2004-08-31 16:49:16 UTC
    gcc       gcc-3_3-branch                2004-08-31 17:03:07 UTC
    gdb       HEAD                          2004-09-02 09:48:18 UTC
    gdb       drow_intercu-20040221-branch  2004-09-02 10:01:01 UTC
    gdb       gdb_6_2-branch                2004-09-02 10:07:35 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, 6.2.0.90, 6.2.1, gdb_6_2-branch, HEAD, drow_intercu-20040221-branch
  suite      => 6.2, 6.2.0.90, 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 gcc-3_3-branch, gcc 3.4.1, gcc 3.4.2-20040829, gcc 3.4.2-20040902, 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      => 298

  '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 suite 6.2, gdb 6.2.0.90 suite 6.2.0.90, 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.

. Host Software

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

    make 3.79.1
    binutils 2.15
    gcc 3.3.4
    flex 2.5.4
    bison 1.875
    texinfo 4.7
    tcl 8.4.6
    expect 5.41
    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.4.2-20040902.

  I added gdb 6.2.0.90.

  I added gdb 6.2.1.

  This is the last spin for gcc 3.4.1, gcc 3.4.2-20040829, and gcc
  3.4.2-200409092.

  This is the last spin for gdb 6.2 and gdb 6.2.0.90.


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