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

  I added gdb 6.2, skipping 6.1.91, 6.1.92, and 6.1.93.  There is one
  regression from gdb 6.1.1 to gdb 6.2: PR gdb/1650.  To see all the
  changes from gdb 6.1.1 to gdb 6.2, look at the difference tables for
  gdb (6.1.1, 6.2).

  gdb.threads/watchthreads.exp is unstable in my test bed.  I have not
  analyzed this yet.

  gcc HEAD sprouted another new warning: if a C file calls a standard
  library function without including the right header, that draws a
  warning.  That broke several test programs in gdb.base, most of the
  programs in gdb.mi, and some programs in gdb.threads.  I have already
  fixed gdb.base and am working on gdb.mi and gdb.threads.  See PR
  gdb/1742, PR gdb/1743.

  Zack Weinberg fixed two debug info regressions in gcc gcc-3_4-branch
  and gcc HEAD.

  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
    no improvements and regressions

  gdb 6.2 versus gdb 6.1.1
    gdb/1650

. Gcc Regression Summary

  gcc HEAD versus gcc 3.4.1
    gcc/13974 gcc/14049
    gdb/1656 gdb/1734 gdb/1735

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

  . gcc HEAD

    http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14860
    [regression] gcc -gstabs+ fails to emit stabs for fundamental types

      Zack Weinberg fixed it.

  . gcc gcc-3_4-branch

    http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13956
    [3.4/3.5 regression] incorrect stabs for nested local variables

      Zack Weinberg fixed it.  This was fixed in both gcc HEAD and
      gcc gcc-3_4-branch.

  . gdb HEAD

    . gdb.base/sep.exp: breakpoint inside included file
      gdb.base/sep.exp: list using location inside included file
        FAIL -> PASS

        Someone fixed a bug in gdb.

. New Bugs Detected Since Last Spin

  . suite HEAD

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

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

      gcc HEAD sprouted a new warning.

. PR Count

. Libiberty Testing

  Query executed 2004-08-11 13:30:08 UTC

  1743 matches found
    20 analyzed
   823 closed
    24 feedback
   856 open
     3 paperwork
    17 suspended
  1743 TOTAL

  . 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-08-07/index.html

  The previous tables are at

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

  . Non-Pass Results

    gdb 6.1.1
      suite 6.1.1                         1482 non-PASS results
      suite HEAD                          1373 non-PASS results
    gdb 6.2
      suite 6.2                           1492 non-PASS results
      suite HEAD                          1363 non-PASS results
    gdb gdb_6_2-branch
      suite gdb_6_2-branch                1485 non-PASS results
      suite HEAD                          1364 non-PASS results
    gdb HEAD
      suite HEAD                          1363 non-PASS results
    gdb drow_intercu-20040221-branch
      suite drow_intercu-20040221-branch  1508 non-PASS results
      suite HEAD                          1376 non-PASS results

  . gdb 6.1.1

    . suite 6.1.1

      . gdb.base/scope.exp: print localval, outer scope
          FAIL -> PASS

          This happened with gcc gcc-3_4-branch -gstabs+
          and gcc HEAD -gstabs+.

          Zack Weinberg fixed a bug in gcc.

            http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13956
            [3.4/3.5 regression] incorrect stabs for nested local variables

      . gdb.mi/mi-var-block.exp: create local variable foo
        gdb.mi/mi-var-block.exp: delete var foo
        gdb.mi/mi2-var-block.exp: create local variable foo
        gdb.mi/mi2-var-block.exp: delete var foo
          FAIL -> PASS

          This happened with gcc gcc-3_4-branch -gstabs+.

          Zack Weinberg fixed a bug in gcc.

            http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13956
            [3.4/3.5 regression] incorrect stabs for nested local variables

      . gdb.base/call-strs.exp: *
        gdb.base/callfuncs.exp: *
        gdb.base/completion.exp: *
        gdb.base/constvars.exp: *
        gdb.base/dbx.exp: *
        gdb.base/maint.exp: *
        gdb.base/miscexprs.exp: *
        gdb.base/opaque.exp: *
        gdb.base/pointers.exp: *
        gdb.base/printcmds.exp: *
        gdb.base/ptype.exp: *
        gdb.base/volatile.exp: *
        gdb.base/whatis-exp.exp: *
        gdb.base/whatis.exp: *
          FAIL -> PASS
          FAIL -> XFAIL

          This happened with gcc HEAD -gstabs+.

          Zack Weinberg fixed a bug in gcc.

            http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14860
            [regression] gcc -gstabs+ fails to emit stabs for fundamental types

      . gdb.base/charset.exp: *
        gdb.base/complex.exp: *
        gdb.base/freebpcmd.exp: *
        gdb.base/gcore.exp: *
        gdb.mi/gdb669.exp: *
        gdb.mi/gdb701.exp: *
        gdb.mi/mi-basics.exp: *
        gdb.mi/mi-break.exp: *
        gdb.mi/mi-cli.exp: *
        gdb.mi/mi-disassemble.exp: *
        gdb.mi/mi-eval.exp: *
        gdb.mi/mi-file.exp: *
        gdb.mi/mi-pthreads.exp: *
        gdb.mi/mi-regs.exp: *
        gdb.mi/mi-return.exp: *
        gdb.mi/mi-simplerun.exp: *
        gdb.mi/mi-stack.exp: *
        gdb.mi/mi-stepi.exp: *
        gdb.mi/mi-var-block.exp: *
        gdb.mi/mi-var-child.exp: *
        gdb.mi/mi-var-cmd.exp: *
        gdb.mi/mi-var-display.exp: *
        gdb.mi/mi-watch.exp: *
        gdb.mi/mi2-basics.exp: *
        gdb.mi/mi2-break.exp: *
        gdb.mi/mi2-cli.exp: *
        gdb.mi/mi2-disassemble.exp: *
        gdb.mi/mi2-eval.exp: *
        gdb.mi/mi2-file.exp: *
        gdb.mi/mi2-pthreads.exp: *
        gdb.mi/mi2-regs.exp: *
        gdb.mi/mi2-return.exp: *
        gdb.mi/mi2-simplerun.exp: *
        gdb.mi/mi2-stack.exp: *
        gdb.mi/mi2-stepi.exp: *
        gdb.mi/mi2-var-block.exp: *
        gdb.mi/mi2-var-child.exp: *
        gdb.mi/mi2-var-cmd.exp: *
        gdb.mi/mi2-var-display.exp: *
        gdb.mi/mi2-watch.exp: *
        gdb.threads/gcore-thread.exp: *
        gdb.threads/killed.exp: *
        gdb.threads/pthreads.exp: *
          blank -> ERROR
          blank -> WARNING
          blank -> NOTE
          blank -> FAIL
          blank -> UNRESOLVED
          blank -> UNSUPPORTED
          PASS -> blank
          PASS -> FAIL
          PASS -> UNRESOLVED
          PASS -> UNSUPPORTED
          FAIL -> blank

          This happened with gdb HEAD.

          gdb HEAD sprouted a new warning:

            warning: incompatible implicit declaration of built-in function 'malloc'

          This happens with many standard c library functions if
          the appropriate standard header has not been included.

          I have already fixed this in suite HEAD for gdb.base/*.c .
          I filed PR's for gdb.mi/*.c and gdb.threads/*.c .

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

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

      . 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/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 non-gcc-HEAD configurations except for
          the "thread N ran" tests.  Here are the counts per thread.

                   t0  t1  t2  t3  t4  t5
            PASS    2  22  21  22  21  22
            FAIL   20   0   1   0   1   0

  . gdb 6.1.1

    . suite HEAD

      . gdb.arch/i386-prologue.exp: continue to standard
        gdb.arch/i386-prologue.exp: backtrace in standard
        gdb.arch/i386-prologue.exp: saved registers in standard
          blank -> PASS

          Mark Kettenis enhanced the test script.

      . gdb.base/auxv.exp: tbreak 45
          PASS -> blank
        gdb.base/auxv.exp: tbreak 66
          blank -> PASS

          Michael Chastain improved the test script.

      . gdb.base/call-sc.exp: *
        gdb.base/call-strs.exp: *
        gdb.base/callfuncs.exp: *
        gdb.base/completion.exp: *
        gdb.base/constvars.exp: *
        gdb.base/dbx.exp: *
        gdb.base/maint.exp: *
        gdb.base/miscexprs.exp: *
        gdb.base/opaque.exp: *
        gdb.base/pointers.exp: *
        gdb.base/printcmds.exp: *
        gdb.base/ptype.exp: *
        gdb.base/volatile.exp: *
        gdb.base/whatis-exp.exp: *
        gdb.base/whatis.exp: *
        gdb.stabs/exclfwd.exp: *
          blank -> PASS
          PASS -> blank
          FAIL -> PASS
          FAIL -> XFAIL

          Same analysis as gdb 6.1.1 suite 6.1.1.

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

          Andrew Cagney overhauled and improved the test scripts.

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

          Fluctuation with unknown cause.  Probably harmless.

      . gdb.base/scope.exp: print localval, outer scope
          FAIL -> PASS

          Same analysis as gdb 6.1.1 suite 6.1.1.

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

          Same analysis as gdb 6.1.1 suite 6.1.1.

      . gdb.mi/mi-var-block.exp: create local variable foo
        gdb.mi/mi-var-block.exp: delete var foo
        gdb.mi/mi2-var-block.exp: create local variable foo
        gdb.mi/mi2-var-block.exp: delete var foo
          FAIL -> PASS

          Same analysis as gdb 6.1.1 suite 6.1.1.

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

          Same analysis as gdb 6.1.1 suite 6.1.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 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  10  10   9  10  10
            FAIL    9   0   0   1   0   0

      . gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
        gdb.threads/watchthreads.exp: watchpoint on args[0] hit in thread
          FAIL -> PASS
        gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
        gdb.threads/watchthreads.exp: watchpoint on args[1] hit in thread
          PASS -> FAIL
          FAIL -> PASS

          Not analyzed.  Probably harmful.

  . gdb gdb_6_2-branch

    . suite gdb_6_2-branch 

      . gdb.base/auxv.exp: *
        gdb.base/charset.exp: *
        gdb.base/complex.exp: *
        gdb.base/freebpcmd.exp: *
        gdb.base/gcore.exp: *
        gdb.base/long_long.exp: *
        gdb.base/sigaltstack.exp: *
        gdb.base/siginfo.exp: *
        gdb.base/sigstep.exp: *
        gdb.mi/*.exp: *
        gdb.threads/*.exp: *
          * -> *

          Same analysis as gdb 6.1.1 suite 6.1.1.

      . gdb.base/call-sc.exp: *
        gdb.base/call-strs.exp: *
        gdb.base/callfuncs.exp: *
        gdb.base/completion.exp: *
        gdb.base/constvars.exp: *
        gdb.base/dbx.exp: *
        gdb.base/maint.exp: *
        gdb.base/miscexprs.exp: *
        gdb.base/opaque.exp: *
        gdb.base/pointers.exp: *
        gdb.base/printcmds.exp: *
        gdb.base/ptype.exp: *
        gdb.base/volatile.exp: *
        gdb.base/whatis-exp.exp: *
        gdb.base/whatis.exp: *
        gdb.stabs/exclfwd.exp: *
          blank -> PASS
          PASS -> blank
          FAIL -> PASS
          FAIL -> XFAIL

          Same analysis as gdb 6.1.1 suite 6.1.1.

      . gdb.base/scope.exp: print localval, outer scope
          FAIL -> PASS

          Same analysis as gdb 6.1.1 suite 6.1.1.

      . gdb.mi/mi-var-block.exp: create local variable foo
        gdb.mi/mi-var-block.exp: delete var foo
        gdb.mi/mi2-var-block.exp: create local variable foo
        gdb.mi/mi2-var-block.exp: delete var foo
          FAIL -> PASS

          Same analysis as gdb 6.1.1 suite 6.1.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

          This is a bug in gdb.  It happens intermittently.

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

      . 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 non-gcc-HEAD configurations except for
          the "thread N ran" tests.  Here are the counts per thread.

                   t0  t1  t2  t3  t4  t5
            PASS    4  20  21  19  19  22
            FAIL   18   2   1   3   3   0

  . gdb gdb_6_2-branch

    . suite HEAD

      . gdb.arch/i386-prologue.exp: *
        gdb.base/auxv.exp: *
        gdb.base/dump.exp: *
        gdb.base/store.exp: *
          * -> *

          Same analyses as gdb 6.1.1 suite HEAD.

      . gdb.base/call-sc.exp: *
        gdb.base/call-strs.exp: *
        gdb.base/callfuncs.exp: *
        gdb.base/completion.exp: *
        gdb.base/constvars.exp: *
        gdb.base/dbx.exp: *
        gdb.base/maint.exp: *
        gdb.base/miscexprs.exp: *
        gdb.base/opaque.exp: *
        gdb.base/pointers.exp: *
        gdb.base/printcmds.exp: *
        gdb.base/ptype.exp: *
        gdb.base/volatile.exp: *
        gdb.base/whatis-exp.exp: *
        gdb.base/whatis.exp: *
        gdb.stabs/exclfwd.exp: *
          blank -> PASS
          PASS -> blank
          FAIL -> PASS
          FAIL -> XFAIL

          Same analysis as gdb 6.1.1 suite 6.1.1.

      . gdb.base/scope.exp: print localval, outer scope
          FAIL -> PASS

          Same analysis as gdb 6.1.1 suite 6.1.1.

      . 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.1.1 suite 6.1.1.

      . gdb.mi/mi-var-block.exp: create local variable foo
        gdb.mi/mi-var-block.exp: delete var foo
        gdb.mi/mi2-var-block.exp: create local variable foo
        gdb.mi/mi2-var-block.exp: delete var foo
          FAIL -> PASS

          Same analysis as gdb 6.1.1 suite 6.1.1.

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

          Same analysis as gdb 6.1.1 suite 6.1.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 gdb_6_2-branch suite gdb_6_2-branch.

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

          Same analysis as gdb 6.1.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 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   9  10  10  10  10
            FAIL    9   1   0   0   0   0

      . gdb.threads/watchthreads.exp: watchpoint on args[0] hit in thread
        gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
          PASS -> FAIL
          FAIL -> PASS

          Not analyzed.  Probably harmful.

  . gdb 6.2

    This is the first spin for gdb 6.2.
      
    . suite 6.2

      Not analyzed.

    . suite HEAD

      I compared gdb 6.2 suite HEAD with gdb gdb_6_2-branch suite HEAD.
      There were no significant differences.

  . gdb HEAD

    . suite HEAD

      . gdb.arch/i386-prologue.exp: *
        gdb.base/auxv.exp: *
        gdb.base/dump.exp: *
        gdb.base/store.exp: *
          * -> *

          Same analyses as gdb 6.1.1 suite HEAD.

      . gdb.base/call-sc.exp: *
        gdb.base/call-strs.exp: *
        gdb.base/callfuncs.exp: *
        gdb.base/completion.exp: *
        gdb.base/constvars.exp: *
        gdb.base/dbx.exp: *
        gdb.base/maint.exp: *
        gdb.base/miscexprs.exp: *
        gdb.base/opaque.exp: *
        gdb.base/pointers.exp: *
        gdb.base/printcmds.exp: *
        gdb.base/ptype.exp: *
        gdb.base/volatile.exp: *
        gdb.base/whatis-exp.exp: *
        gdb.base/whatis.exp: *
        gdb.stabs/exclfwd.exp: *
          blank -> PASS
          PASS -> blank
          FAIL -> PASS
          FAIL -> XFAIL

          Same analysis as gdb 6.1.1 suite 6.1.1.

      . gdb.base/scope.exp: print localval, outer scope
          FAIL -> PASS

          Same analysis as gdb 6.1.1 suite 6.1.1.

      . gdb.base/sep.exp: breakpoint inside included file
        gdb.base/sep.exp: list using location inside included file
          FAIL -> PASS

          Someone fixed a bug in gdb.  These tests results were PASS
          on all configurations tested.

      . gdb.mi/mi-file.exp: Getting a list of source files.
          FAIL -> PASS

          This looks accidental to me.  This test requires a list of
          files starting with the source file and including at least
          four more files.  (It accepts more than four files because of
          greedy ".*" matching).

            # gdb HEAD 2004-08-01
            # gcc 2.95.3, binutils 2.15, dwarf-2
            files=[
              {file="/berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.mi/basics.c",fullname="/berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.mi/basics.c"},
              {file=""},
              {file=""},
              {file="init.c"}
              ]

            # gdb HEAD 2004-08-07
            # gcc 2.95.3, binutils 2.15, dwarf-2
            files=[
              {file="/berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.mi/basics.c",fullname="/berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.mi/basics.c"},
              {file="/tmp/ccqfJNVk.s"},
              {file=""},
              {file="/tmp/ccnhFcil.s"},
              {file=""},
              {file="init.c"}
              ]

          I mistrust that this is really an improvement in gdb.

          Here is a pass/fail table for this test by gcc version
          and debug format.

          Last spin:

                                  dwarf-2  stabs+
            gcc 2.95.3            fail     fail
            gcc 3.2-7-rh          fail     PASS
            gcc 3.3.4             fail     PASS
            gcc gcc-3_3-branch    fail     PASS
            gcc 3.4.1             fail     fail
            gcc gcc-3_4-branch    fail     fail
            gcc HEAD              fail     fail

          This spin:

                                  dwarf-2  stabs+
            gcc 2.95.3            PASS     PASS
            gcc 3.2-7-rh          PASS     PASS
            gcc 3.3.4             PASS     PASS
            gcc gcc-3_3-branch    PASS     PASS
            gcc 3.4.1             PASS     PASS
            gcc gcc-3_4-branch    PASS     PASS
            gcc HEAD              fail     fail

      . gdb.mi/mi-var-block.exp: create local variable foo
        gdb.mi/mi-var-block.exp: delete var foo
        gdb.mi/mi2-var-block.exp: create local variable foo
        gdb.mi/mi2-var-block.exp: delete var foo
          FAIL -> PASS

          Same analysis as gdb 6.1.1 suite 6.1.1.

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

          Same analysis as gdb 6.1.1 suite 6.1.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 gdb_6_2-branch suite gdb_6_2-branch.

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

          Same analysis as gdb 6.1.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 non-gcc-HEAD configurations except for
          the "thread N ran" tests.  Here are the counts per thread.

                   t0  t1  t2  t3  t4  t5
            PASS    2  20  22  22  22  22
            FAIL   20   2   0   0   0   0

      . gdb.threads/watchthreads.exp: watchpoint on args[0] hit in thread
        gdb.threads/watchthreads.exp: watchpoint on args[1] hit in thread
        gdb.threads/watchthreads.exp: first watchpoint on args[1] hit
          PASS -> FAIL
          FAIL -> PASS

          Not analyzed.  Probably harmful.

  . gdb drow_intercu-20040221-branch

    The last change on this branch was 2004-04-19.

    . 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-08-06 15:32:49 UTC
    gcc       HEAD                          2004-08-06 16:03:43 UTC
    gcc       gcc-3_4-branch                2004-08-06 16:19:34 UTC
    gcc       gcc-3_3-branch                2004-08-06 16:35:43 UTC
    gdb       HEAD                          2004-08-07 08:51:36 UTC
    gdb       drow_intercu-20040221-branch  2004-08-07 09:04:45 UTC
    gdb       gdb_6_2-branch                2004-08-07 09:12:44 UTC

  . Last Spin

    binutils  HEAD                          2004-07-31 12:53:06 UTC
    gcc       HEAD                          2004-07-31 13:04:19 UTC
    gcc       gcc-3_4-branch                2004-07-31 13:18:10 UTC
    gcc       gcc-3_3-branch                2004-07-31 13:31:33 UTC
    gdb       HEAD                          2004-08-01 09:36:53 UTC
    gdb       drow_intercu-20040221-branch  2004-08-01 09:49:56 UTC
    gdb       gdb_6_2-branch                2004-08-01 09:56: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.1.1, 6.2.2, gdb_6_2-branch, HEAD, drow_intercu-20040221-branch
  suite      => 6.1.1, 6.2.2, 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 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      => 164

  '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 gdb 6.1.1 suite 6.1.1, gdb_6_2-branch suite gdb_6-2-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.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 gdb 6.2.

  This is the last spin for gdb 6.1.1.


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