This is the mail archive of the gcc-testresults@gcc.gnu.org mailing list for the GCC 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

  binutils binutils-2_15-branch has some issues with shared libraries
  that are probably gdb problems, but need some investigation.

  gcc 3.3.3 is available from ftp.gnu.org, although no announcement has
  been made on gcc-announce.  This version of gcc 3.3.3 is healthy.

  My 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 gdb/1563

. Gcc Regression Summary

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

  gcc HEAD versus gcc 3.3.2
    gcc/12267 gcc/13708 gcc/13956 gcc/13974
    gdb/1537 gdb/1540
    classes.exp unanalyzed 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 gcc-3_3-branch versus gcc 3.3.2
  gcc 3.3.3 versus gcc 3.3.2
  gcc 3.3.3-20040210 versus gcc 3.3.2
    No improvements; no regressions.

. Binutils Regression Summary

  binutils HEAD versus binutils 2.14
  binutils binutils-2_15-branch versus binutils 2.14
    gdb.base/gdb1250.exp unanalyzed regressions
    gdb.base/gdb1476.exp unanalyzed regressions
    gdb.base/shlib-call.exp unanalyzed regressions

. Old Bugs Fixed Since Last Spin

  . gdb HEAD

    http://sources.redhat.com/gdb/bugs/1447
    "p/c i386.long_double" doesn't work

      Jeff J partially fixed this.  There is still one KFAIL with this
      with gcc tree-ssa-20020619-branch.

. New Bugs Detected Since Last Spin

  . gdb HEAD

    http://sources.redhat.com/gdb/bugs/1563
    Regression printing large integers

. PR Count

  Query executed 2004-02-23 16:07:01 UTC

  1560 matches found
    21 analyzed
   734 closed
    25 feedback
   761 open
     3 paperwork
    16 suspended
  1560 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                  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 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-21/index.html

  The previous tables are at

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

  . Non-Pass Results

    gdb 6.0
      suite 6.0                         459 non-PASS results
      suite HEAD                        618 non-PASS results
    gdb HEAD
      suite HEAD                        464 non-PASS results
    gdb drow-cplus-branch
      suite drow-cplus-branch           611 non-PASS results
      suite HEAD                        590 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

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

                      PASS  FAIL
            thread 0     6    44
            thread 1    48     2
            thread 2    48     2
            thread 3    48     2
            thread 4    47     3
            thread 5    50     0

  . gdb 6.0

    . suite HEAD

      . gdb.base/bigcore.exp: *
          blank -> PASS
        gdb.base/bigcore.exp: check next heap
        gdb.base/bigcore.exp: check prev heap
          blank -> FAIL

          Andrew C wrote a new test script.

      . gdb.base/callfuncs.exp: call inferior func with struct -  returns short
          PASS -> blank
      . gdb.base/callfuncs.exp: call inferior func with struct - returns short
          blank -> PASS

          Fred F fixed a typo in the test script.

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

          Fluctuation with unknown cause.

      . gdb.base/freebpcmd.exp: run program with breakpoint commands
          KFAIL -> PASS
          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.base/gdb1555.exp: *
          blank -> PASS

          Adam F wrote a new test script.

      . gdb.objc/basicclass.exp: Call an Objective-C method with no arguments
          PASS -> FAIL

          Ulrich W changed the test script so that it accepts the output
          of gdb HEAD and does not accept the output of gdb 6.0.
          gdb 6.0 is still okay.

      . 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    14
            thread 1    14     2
            thread 2    15     1
            thread 3    16     0
            thread 4    16     0
            thread 5    16     0

  . gdb HEAD

    . suite HEAD

      . gdb.base/bigcore.exp: *
          blank -> PASS
        gdb.base/bigcore.exp: check next heap
        gdb.base/bigcore.exp: check prev heap
          blank -> FAIL

          Same analysis as gdb 6.0 suite HEAD.

      . gdb.base/callfuncs.exp: call inferior func with struct -  returns short
          PASS -> blank
      . gdb.base/callfuncs.exp: call inferior func with struct - returns short
          blank -> PASS

          Same analysis as gdb 6.0 suite HEAD.

      . gdb.base/gdb1555.exp: *
          blank -> PASS

          Same analysis as gdb 6.0 suite HEAD.

      . gdb.base/structs.exp: p/c L<n>; call * structs-*tld*
        gdb.base/structs.exp: p/c fun<n>; call * structs-*tld*
        gdb.base/structs.exp: value foo<n> finished; return 1 structs-tld
        gdb.base/structs.exp: value foo<n> returned; return 1 structs-tld
        gdb.base/structs.exp: zed L<n> for finish; return 1 structs-tld
        gdb.base/structs.exp: zed L<n> for return; return 1 structs-tld
          KFAIL -> KPASS

            Jeff J partially fixed a bug in gdb.

              http://sources.redhat.com/gdb/bugs/1447
              "p/c i386.long_double" doesn't work

            One test still KFAIL'ed with gcc tree-ssa-20020619-branch,
            both dwarf-2 and stabs+.

              # gdb.log
              (gdb) next
              439           L2  = fun2();     
              (gdb) PASS: gdb.base/structs.exp: return foo<n>; return 1 structs-tld
              p/c L1
              $6 = {a = 0 '\0'}
              (gdb) KFAIL: gdb.base/structs.exp: value foo<n> returned; return 1 structs-tld (

      . 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.java/jmisc.exp: program timed out
          WARNING -> blank
        gdb.java/jmisc.exp: *
          * -> *

          In the previous spin, one configuration of gdb timed out while
          running gcj.  This timeout did not recur.

      . gdb.stabs/weird.exp: print very big integer
          PASS -> FAIL

          gdb changed its behavior.

            # gdb.log
            p/x int256var^M
            $177 = 0x0000002a0000002b0000002c0000002d0000002d0000002c0000002b0000002a^M
            (gdb) PASS: gdb.stabs/weird.exp: print very big integer

            # gdb.log
            p/x int256var^M
            $177 = That operation is not available on integers of more than 8 bytes.^M
            (gdb) FAIL: gdb.stabs/weird.exp: print very big integer

          However, "print int256var" works fine.

          Daniel J filed a PR on this:

            http://sources.redhat.com/gdb/bugs/1563
            Regression printing large integers

      . 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     4    46
            thread 1    47     3
            thread 2    50     0
            thread 3    49     1
            thread 4    49     1
            thread 5    50     0

  . gdb drow-cplus-branch

    . suite drow-cplus-branch

      . gdb.base/pending.exp: pending plus condition
          FAIL -> PASS
          PASS -> FAIL

          Not analyzed.

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

          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     1    15
            thread 1    12     4
            thread 2    16     0
            thread 3    16     0
            thread 4    16     0
            thread 5    16     0

  . gdb drow-cplus-branch

    . suite HEAD

      . gdb.base/bigcore.exp: *
          blank -> PASS
        gdb.base/bigcore.exp: check next heap
        gdb.base/bigcore.exp: check prev heap
          blank -> FAIL

          Same analysis as gdb 6.0 suite HEAD.

      . gdb.base/callfuncs.exp: call inferior func with struct -  returns short
          PASS -> blank
      . gdb.base/callfuncs.exp: call inferior func with struct - returns short
          blank -> PASS

          Same analysis as gdb 6.0 suite HEAD.

      . gdb.base/gdb1555.exp: *
          blank -> PASS

          Same analysis as gdb 6.0 suite HEAD.

      . gdb.objc/basicclass.exp: Call an Objective-C method with no arguments
          PASS -> FAIL

          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    16
            thread 1    16     0
            thread 2    16     0
            thread 3    16     0
            thread 4    16     0
            thread 5    16     0

. Package Versions

  . This Spin

    binutils  HEAD                       2004-02-20 04:30:06 UTC
    binutils  binutils-2_15-branch       2004-02-20 04:31:40 UTC
    gcc       tree-ssa-20020619-branch   2004-02-20 04:36:00 UTC
    gcc       HEAD                       2004-02-20 04:42:39 UTC
    gcc       gcc-3_4-branch             2004-02-20 04:48:22 UTC
    gcc       gcc-3_3-branch             2004-02-20 04:54:22 UTC
    gdb       HEAD                       2004-02-21 10:34:37 UTC
    gdb       drow-cplus-branch          2004-02-21 10:38:45 UTC

  . Last Spin

    binutils  HEAD                       2004-02-14 10:07:33 UTC
    gcc       tree-ssa-20020619-branch   2004-02-14 10:18:26 UTC
    gcc       HEAD                       2004-02-14 10:30:59 UTC
    gcc       gcc-3_4-branch             2004-02-14 10:36:50 UTC
    gcc       gcc-3_3-branch             2004-02-14 10:46:11 UTC
    gdb       HEAD                       2004-02-15 06:12:22 UTC
    gdb       carlton_dictionary-branch  2004-02-15 06:15:06 UTC
    gdb       drow-cplus-branch          2004-02-15 06:16:58 UTC

. 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, drow-cplus-branch
  suite      => 6.0, drow-cplus-branch, HEAD
  cc         => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.2, gcc 3.3.3-20040210, gcc 3.3.3, 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 binutils-2_15-branch, binutils HEAD
  ld         => binutils 2.13.90.0.2-rh, binutils 2.14, binutils binutils-2_15-branch, binutils HEAD
  libc       => glibc 2.2.93-5-rh
  gformat    => dwarf-2, stabs+
  glevel     => 2
  count      => 148

  '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 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
  drow-cplus-branch with vendor cc at all.

  I test each version gdb with its own gdb-test-suite and also with
  gdb-test-suite HEAD.  When I test a non-HEAD gdb with suite HEAD,
  I test only with binutils 2.14.

. 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 dropped gdb carlton_dictionary-branch.

  I dropped configurations with gdb 6.0, suite HEAD, binutils HEAD.
  binutils HEAD is covered by gdb 6.0 suite 6.0 and gdb HEAD suite HEAD.

  I added gcc 3.3.3 from ftp.gnu.org.  This is not an official release
  yet because no annoucement has been made on gcc.announce.

  I added binutils binutils-2_15-branch.

  If this version of gcc 3.3.3 is not withdrawn, then I will drop
  gcc 3.3.2 and gcc 3.3.3-20040210 on the next spin.


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