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

  gcc gcc-3_3-branch 2004-02-01 15:44:58 UTC is okay compared to gcc 3.3.2.
  This is with native i686-pc-linux-gnu, dwarf-2 and stabs+.

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

  The current tables are always at

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

. Old Bugs Fixed

  . gdb HEAD

    http://sources.redhat.com/gdb/bugs/1511
    lookup_transparent_type sometimes fails in presence of classes in namespaces

      Fixed with gcc gcc-3_4-branch -gdwarf-2 and gcc HEAD -gdwarf-2.
      Still happens with gcc 3.2.* -gdwarf-2 and gcc 3.3.* -gdwarf-2.

. New Bugs Detected

  None.

. PR Count

  Query executed 2004-02-03 14:19:14 UTC

  1542 matches found
    22 analyzed
   701 closed
    28 feedback
   775 open
     3 paperwork
    13 suspended
  1542 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
      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-02/index.html

  The previous tables are at

    http://www.shout.net/~mec/sunday/2004-01-28/index.html

  . Non-Pass Results

    gdb 6.0
      suite 6.0                         350 non-PASS results
      suite HEAD                        502 non-PASS results
    gdb HEAD
      suite HEAD                        434 non-PASS results
    gdb carlton_dictionary-branch
      suite carlton_dictionary-branch   430 non-PASS results
      suite HEAD                        422 non-PASS results
    gdb drow-cplus-branch
      suite drow-cplus-branch           653 non-PASS results
      suite HEAD                        584 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.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]
          blank -> PASS
          PASS -> blank

          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/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     1    25
            thread 1    26     0
            thread 2    26     0
            thread 3    25     1
            thread 4    25     1
            thread 5    26     0

    . suite HEAD

      . gdb.base/chng-syms.exp: *
          blank -> PASS

          Paul H wrote a new test script.

      . gdb.base/completion.exp: complete-command 'file ./gdb.base/compl'
          blank -> FAIL

          Jim I wrote a new test.

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

          Same analysis as gdb 6.0 suite 6.0.

      . gdb.cp/inherit.exp: print g_vE
          PASS -> FAIL

          Michael C de-improved the test.
          This happened with gcc 3.2-7-rh -gstabs+.

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

          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     3    23
            thread 1    25     1
            thread 2    26     0
            thread 3    24     2
            thread 4    24     2
            thread 5    26     0

      . gdb.threads/thread-specific.exp: *
          blank -> PASS
        gdb.threads/thread-specific.exp: continue to thread-specific breakpoint (wrong breakpoint)
          blank -> FAIL

          Daniel J wrote a new test script.

  . gdb HEAD

    . suite HEAD

      . gdb.base/chng-syms.exp: *
          blank -> PASS

          Same analysis as gdb 6.0 suite HEAD.

      . gdb.base/completion.exp: complete-command 'file ./gdb.base/compl'
          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

          Same analysis as gdb 6.0 suite 6.0.

      . gdb.cp/inherit.exp: print g_vE
          PASS -> FAIL

          Same analysis as gdb 6.0 suite HEAD.

      . gdb.cp/rtti.exp: print *e2
          KFAIL -> PASS
        gdb.cp/rtti.exp: print *obj
          FAIL -> PASS

          This happened with gcc gcc-3_4-branch -gdwarf-2 and gcc HEAD
          -gdwarf-2.  Someone improved gdb.

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

          Same analysis as gdb 6.0 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.

                      PASS  FAIL
            thread 0     5    21
            thread 1    25     1
            thread 2    24     2
            thread 3    24     2
            thread 4    24     2
            thread 5    26     0

      . gdb.threads/thread-specific.exp: *
          blank -> PASS

          Same analysis as gdb 6.0 suite HEAD.

  . gdb carlton_dictionary-branch

    . suite carlton_dictionary-branch

      . 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     3     9
            thread 1     7     5
            thread 2    10     2
            thread 3    11     1
            thread 4    11     1
            thread 5    12     0

    . suite HEAD

      . gdb.base/chng-syms.exp: *
          blank -> PASS

          Same analysis as gdb 6.0 suite HEAD.

      . gdb.base/completion.exp: complete-command 'file ./gdb.base/compl'
          blank -> FAIL

          Same analysis as gdb 6.0 suite HEAD.

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

          Same analysis as gdb 6.0 suite 6.0.

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

          Same analysis as gdb 6.0 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.

                      PASS  FAIL
            thread 0     0    12
            thread 1    12     0
            thread 2    12     0
            thread 3    12     0
            thread 4    12     0
            thread 5    12     0

      . gdb.threads/thread-specific.exp: *
          blank -> PASS
        gdb.threads/thread-specific.exp: continue to thread-specific breakpoint (wrong breakpoint)
          blank -> FAIL

          Same analysis as gdb 6.0 suite HEAD.

  . gdb drow-cplus-branch

    . suite drow-cplus-branch

      . 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    10
            thread 1    12     0
            thread 2    11     1
            thread 3    11     1
            thread 4    10     2
            thread 5    12     0

    . suite HEAD

      . gdb.base/chng-syms.exp: *
          blank -> PASS

          Same analysis as gdb 6.0 suite HEAD.

      . gdb.base/completion.exp: complete-command 'file ./gdb.base/compl'
          blank -> FAIL

          Same analysis as gdb 6.0 suite HEAD.

      . gdb.cp/inherit.exp: *
          * -> *
        gdb.cp/local.exp: running to main in runto (timeout)
          FAIL -> UNRESOLVED

          This script bombs on gcc 2.95.3 -gstabs+, along with many
          other scripts.  gdb has the same problem as last spin; the
          test script reacts differently from last spin.

            # gdb.log excerpt
            (gdb) break main
            Orig expression: ._1::._1
            A syntax error in expression, near `._1::._1'.
            WARNING: remote_expect statement without a default case?!

          There were also several regressions with gcc 3.* -gstabs+
          caused by changes in inherit.exp.  gdb drow-cplus-branch
          prints slightly different output than gdb HEAD for v3
          synthetic constructors.  gdb HEAD prints "vB()" and gdb
          drow-cplus-branch prints "vB(void)", and the test script needs
          to accept both forms.

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

          Same analysis as gdb 6.0 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.

                      PASS  FAIL
            thread 0     2    10
            thread 1    11     1
            thread 2    12     0
            thread 3    11     1
            thread 4    10     2
            thread 5    12     0

      . gdb.threads/thread-specific.exp: *
          blank -> PASS
        gdb.threads/thread-specific.exp: continue to thread-specific breakpoint (wrong breakpoint)
          blank -> FAIL

          Same analysis as gdb 6.0 suite HEAD.

. Test Matrix

  target     => native
  host       => i686-pc-linux-gnu
  osversion  => red-hat-8.0
  dejagnu    => dejagnu 1.4.3
  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 gcc-3_3-branch, gcc gcc-3_4-branch, gcc HEAD
  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         126

  '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-01 15:27:25 UTC
    gcc       HEAD                       2004-02-01 15:37:18 UTC
    gcc       gcc-3_3-branch             2004-02-01 15:44:58 UTC
    gcc       gcc-3_4-branch             2004-02-01 15:51:06 UTC
    gdb       HEAD                       2004-02-02 10:05:57 UTC
    gdb       carlton_dictionary-branch  2004-02-02 10:08:17 UTC
    gdb       drow-cplus-branch          2004-02-02 10:10:16 UTC

  . Last Spin

    binutils  HEAD                       2004-01-27 09:05:46 UTC
    gcc       HEAD                       2004-01-27 09:18:37 UTC
    gcc       gcc-3_3-branch             2004-01-27 09:26:38 UTC
    gcc       gcc-3_4-branch             2004-01-27 09:34:08 UTC
    gdb       HEAD                       2004-01-28 05:33:45 UTC (approximate)
    gdb       carlton_dictionary-branch  2004-01-28 05:34:40 UTC
    gdb       drow-cplus-branch          2004-01-28 05:38:59 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 upgraded from dejagnu 1.4.3 to dejagnu 1.4.4.  I did before-and-after
  spins and found no differences.

  I dropped vendor binutils (binutils 2.13.90.0.2-rh), except with
  vendor gcc (gcc 3.2-7-rh).

  I added gcc 3.3.3-20040131.


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