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 regressions in binutils, gcc, gdb.

  I added gcc 3.3.4-20040530.  It's healthy.  There are no debug info
  regressions versus gcc 3.3.4 with dwarf-2 and stabs+.

  The checkout dates of the various gdb versions are more spread out
  than usual.  See the "Package Versions" section for more info.

  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
    gdb.arch/i386-prologue.exp: check jump_at_beginning prologue end
    gdb.base/call-sc.exp: return foo; return call-sc-tld
    gdb.base/call-sc.exp: value foo returned; return call-sc-td
    gdb.base/call-sc.exp: value foo returned; return call-sc-tf
    gdb.base/call-sc.exp: value foo returned; return call-sc-tld

  gdb HEAD versus gdb 6.1
    gdb/1444 gdb/1613 gdb/1650

  gdb gdb_6_1-branch versus gdb 6.1
    no improvements and no regressions

. Gcc Regression Summary

  gcc HEAD versus gcc 3.4.0
    gcc/13974 gcc/14048 gcc/14049 gcc/14860 gcc/15721
    gdb/1656

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

  gcc 3.4.0 versus gcc 3.3.3
    gcc/12267 gcc/13708 gcc/13956
    gdb/1537 gdb/1540

  gcc gcc-3_3-branch versus gcc 3.3.3
  gcc 3.3.4-20040530 versus gcc 3.3.3
  gcc 3.3.4-20040517 versus gcc 3.3.3
    no improvements and no regressions

  gcc 3.3.3 versus gcc 2.95.3
    not analyzed

. Binutils Regression Summary

  binutils HEAD versus binutils 2.15
  binutils binutils_2-15-branch versus binutils 2.15
    no improvements and no regressions

. Old Bugs Fixed Since Last Spin

  None.

. New Bugs Fixed Since Last Spin

  None.

. PR Count

  Query executed 2004-06-05 02:18:49 UTC

  1662 matches found
    21 analyzed
   771 closed
    23 feedback
   827 open
     3 paperwork
    17 suspended
  1662 TOTAL

. Libiberty Testing

  . target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
      binutils binutils-2_15-branch     742 tests, 0 failures
      binutils HEAD                     745 tests, 0 failures
      gcc gcc-3_3-branch                649 tests, 0 failures
      gcc gcc-3_4-branch                745 tests, 0 failures
      gcc HEAD                          745 tests, 0 failures
      gdb HEAD                          745 tests, 0 failures
      gdb drow_intercu-20040221-branch  745 tests, 0 failures
      gdb gdb_6_1-branch                745 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-06-01/index.html

  The previous tables are at

    http://www.shout.net/~mec/sunday/2004-05-25/index.html

  . Non-Pass Results

    gdb 6.1
      suite 6.1                           1030 non-PASS results
      suite HEAD                          1065 non-PASS results
    gdb gdb_6_1-banch
      suite gdb_6_1-branch                1033 non-PASS results
      suite HEAD                          1064 non-PASS results
    gdb HEAD
      suite HEAD                          1101 non-PASS results
    gdb drow_intercu-20040221-branch
      suite drow_intercu-20040221-branch  1044 non-PASS results
      suite HEAD                          1075 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.1

    . suite 6.1

      . 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/print-threads.exp: Hit kill breakpoint, 10 (slow with kill breakpoint)
          blank -> PASS
        gdb.threads/print-threads.exp: Hit kill breakpoint, 11 (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.

                   t0  t1  t2  t3  t4  t5
            PASS    2  50  50  50  50  50
            FAIL   48   0   0   0   0   0

  . gdb 6.1

    . suite HEAD

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

                   t0  t1  t2  t3  t4  t5
            PASS    1  16  16  16  15  16
            FAIL   15   0   0   0   1   0

  . gdb gdb_6_1-branch

    . suite gdb_6_1-branch

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

          Same analysis as gdb 6.1 suite 6.1.

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

                   t0  t1  t2  t3  t4  t5
            PASS    5  47  50  49  48  50
            FAIL   45   3   0   1   2   0

  . gdb gdb_6_1-branch

    . suite HEAD

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

                   t0  t1  t2  t3  t4  t5
            PASS    1  16  16  16  16  16
            FAIL   15   0   0   0   0   0

  . gdb HEAD

    . suite HEAD

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

          Same analysis as gdb 6.1 suite 6.1.

      . gdb.threads/manythreads.exp: stop threads 1
        gdb.threads/manythreads.exp: stop threads 2
          blank -> PASS
          PASS -> blank
        gdb.threads/manythreads.exp: stop threads 1 (GDB internal error)
        gdb.threads/manythreads.exp: stop threads 2 (GDB internal error)
          blank -> FAIL
          FAIL -> blank

          This is a bug in gdb.  It happens intermittently.

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

      . gdb.threads/print-threads.exp: *
          * -> *

          This test script is useless in suite HEAD.

            http://sources.redhat.com/gdb/bugs/1636
            manythreads.exp issues async ^C that spills onto next script

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

                   t0  t1  t2  t3  t4  t5
            PASS    3  50  50  49  47  50
            FAIL   47   0   0   1   3   0

  . gdb drow_intercu-20040221-branch

    . suite drow_intercu-20040221-branch

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

          Same analysis as gdb 6.1 suite 6.1.

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

                   t0  t1  t2  t3  t4  t5
            PASS    9   7   9  10  11  16
            FAIL    7   9   7   6   5   0

  . gdb drow_intercu-20040221-branch

    . suite HEAD

      . gdb.base/auxv.exp: *
          blank -> PASS
          WARNING -> blank
          FAIL -> PASS
          UNSUPPORTED -> PASS
          UNSUPPORTED -> FAIL

          This is a bug in the test script.
          
            http://sources.redhat.com/gdb/bugs/1647
            gdb.base/auxv.exp, incomplete input consumption

      . gdb.threads/manythreads.exp: stop threads 1
        gdb.threads/manythreads.exp: stop threads 2
          blank -> PASS
          PASS -> blank
        gdb.threads/manythreads.exp: stop threads 1 (GDB internal error)
        gdb.threads/manythreads.exp: stop threads 2 (GDB internal error)
          FAIL -> blank
          blank -> FAIL

          This is a bug in gdb.  It happens intermittently.

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

      . gdb.threads/print-threads.exp: *
          * -> *

          Same analysis as gdb HEAD suite HEAD.

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

                   t0  t1  t2  t3  t4  t5
            PASS    9   7   9  10  11  16
            FAIL    7   9   7   6   5   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.

                   t0  t1  t2  t3  t4  t5
            PASS    3  15  16  16  15  16
            FAIL   13   1   0   0   1   0

. Package Versions

  For this spin, there is a big spread in the checkout dates for the
  different gdb versions.  I do each checkout with "cvs -D ..." and the
  indicated date, so each version is coherent.  They are just more
  separated in time from each other this usual.  (This happened because
  there was a build bug in gdb HEAD, so I had to wait for a fix before
  checking out gdb HEAD).

  . This Spin

    binutils  HEAD                          2004-05-31 02:13:57 UTC
    binutils  binutils-2_15-branch          2004-05-31 02:16:53 UTC
    gcc       HEAD                          2004-05-31 02:21:04 UTC
    gcc       gcc-3_4-branch                2004-05-31 02:28:46 UTC
    gcc       gcc-3_3-branch                2004-05-31 02:36:26 UTC
    gdb       HEAD                          2004-06-03 17:47:54 UTC
    gdb       drow_intercu-20040221-branch  2004-06-01 22:50:50 UTC
    gdb       gdb_6_1-branch                2004-06-03 02:10:47 UTC

  . Last Spin

    binutils  HEAD                          2004-05-24 12:27:55 UTC
    binutils  binutils-2_15-branch          2004-05-24 12:33:22 UTC
    gcc       HEAD                          2004-05-24 12:40:19 UTC
    gcc       gcc-3_4-branch                2004-05-24 12:53:06 UTC
    gcc       gcc-3_3-branch                2004-05-24 13:28:07 UTC
    gdb       HEAD                          2004-05-25 18:22:57 UTC
    gdb       drow_intercu-20040221-branch  2004-05-25 18:29:15 UTC
    gdb       gdb_6_1-branch                2004-05-25 18:32:10 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.1, gdb_6_1-branch, HEAD, drow_intercu-20040221-branch
  suite      => 6.1, gdb_6_1-branch, HEAD, drow_intercu-20040221-branch
  cc         => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.3, gcc 3.3.4-20040517, gcc 3.3.4-20040530, gcc gcc-3_3-branch, gcc 3.4.0, gcc gcc-3_4-branch, gcc HEAD
  as         => binutils 2.13.90.0.2-rh, binutils 2.15, binutils binutils-2_15-branch, binutils HEAD
  ld         => binutils 2.13.90.0.2-rh, binutils 2.15, binutils binutils-2_15-branch, binutils HEAD
  libc       => glibc 2.2.93-5-rh
  gformat    => dwarf-2, stabs+
  glevel     => 2
  count      => 214

  '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 6.1 suite 6.1, gdb gdb_6_1-branch suite gdb_6-1-branch, and gdb
  HEAD suite HEAD with the full spectrum of as and ld.  I test 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.14
    gcc 3.3.3
    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.3.4-20040530.

  This is the last spin for gcc 3.3.4-20040517.


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