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]

sunday project, gdb, 2003-08-07


. Highlights of this report

  Andrew C fixed one of the backtrace bugs for stabs+.

  gcc gcc-3_3-branch continues to be fine.  I will add gcc 3.3.1 in the
  next report.  If gcc 3.3.1 behaves as expected, then I will drop gcc
  3.3 in the report after that.

  The new gdb.mi/mi2-*.exp scripts test mi level 2.  They did their job
  all right: "gdb -i=mi2" seg faults when gdb starts up.  Yikes!

Michael C

. Old Bugs Fixed

  http://sources.redhat.com/gdb/bugs/1250
  [regression] bad backtrace when function that calls 'abort' at end
  (fixed for dwarf-2 and stabs+, still broken with no debugging symbols)

. New Bugs Detected

  The command "gdb -i=mi2" seg faults.
  Andrew C has a fix.

. PR Count

  Query executed 2003-08-08T16:48:23Z

  1327 matches found
    18 analyzed
   588 closed
    20 feedback
   687 open
     3 paperwork
    11 suspended
  1327 TOTAL

. Libiberty Testing

  . target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
      binutils binutils-2_14-branch                      649 tests, 0 failures
      binutils HEAD                                      714 tests, 31 failures
      gcc 2.95.3, binutils binutils-2_14-branch          All 616 tests passed
      gcc 2.95.3, binutils HEAD                          All 616 tests passed
      gcc 3.3, binutils binutils-2_14-branch             649 tests, 0 failures
      gcc 3.3, binutils HEAD                             649 tests, 0 failures
      gcc gcc-3_3-branch, binutils 2.14                  649 tests, 0 failures
      gcc gcc-3_3-branch, binutils binutils-2_14-branch  649 tests, 0 failures
      gcc gcc-3_3-branch, binutils HEAD                  649 tests, 0 failures
      gcc gcc-3_3-branch, binutils vendor                649 tests, 0 failures
      gcc HEAD, binutils 2.14                            714 tests, 31 failures
      gcc HEAD, binutils binutils-2_14-branch            714 tests, 31 failures
      gcc HEAD, binutils HEAD                            714 tests, 31 failures
      gcc HEAD, binutils vendor                          714 tests, 31 failures
      gdb carlton_dictionary-branch                      714 tests, 31 failures
      gdb gdb_6_0-branch                                 649 tests, 0 failures
      gdb HEAD                                           714 tests, 31 failures

    These are long-standing demangler bugs.

      http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7986
      Problems with demangling (__cxa_demangle())

      http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11028
      The standalone C++ demangler doesn't work on some symbols

    A libiberty log is available at

      http://gcc.gnu.org/ml/gcc/2003-07/msg00032.html

. Gdb Testing

  My tables are at

    http://www.shout.net/~mec/sunday/2003-08-07/index.html

  The previous tables are at

    http://www.shout.net/~mec/sunday/2003-08-02/index.html

  . Non-PASS Results

    gdb 5.3             348 non-PASS results
    gdb gdb_6_0-branch  420 non-PASS results
    gdb HEAD            444 non-PASS results

  . 5.3

    . gdb.c++/annota2.exp: annotate-quit

        http://sources.redhat.com/gdb/bugs/544
        gdb.c++/annota2.exp: annotate-quit test sometimes fails

        Fluctuation in test result probably due to a signal handling
        race in the command loop.

    . gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily

        http://sources.redhat.com/gdb/bugs/568
        GDB confused by messily-exiting multi-threaded programs

        Jim B thinks that this test may depend on a race condition:

          http://sources.redhat.com/ml/gdb-testers/2002-q4/msg00010.html

    . gdb.threads/schedlock.exp: *

        This test script is useless in this release because of a
        signed-versus-unsigned bug.

        Daniel J has an obvious fix, which has been applied to gdb HEAD:

          http://sources.redhat.com/ml/gdb-patches/2002-10/msg00454.html

  . gdb_6_0-branch

    checkout date is '2003-08-07 20:31:55 UTC'
    previous date is '2003-08-03 05:24:07 UTC'

    . gdb.base/completion.exp: cd to ${objdir}
      gdb.base/completion.exp: complete 'file ./Make'
        PASS -> blank

        Elena Z removed some troublesome tests.

    . gdb.base/corefile.exp: backtrace in corefile.exp
      gdb.base/corefile.exp: print func2::coremaker_local
        FAIL -> PASS

        Andrew C partially fixed a bug in gdb.

          http://sources.redhat.com/gdb/bugs/1250
          [regression] bad backtrace when function that calls 'abort' at end

        gcc -gdwarf-2 and gcc -stabs+ are fixed, but gcc with no
        debug info is still broken.

    . gdb.mi/mi-pthreads.exp: check mi_thread_command_set: -thread-select 3
      gdb.mi/mi-pthreads.exp: check mi_thread_command_set: -thread-select 4
      gdb.mi/mi-pthreads.exp: check mi_thread_command_set: -thread-select 5
      gdb.mi/mi-pthreads.exp: check mi_thread_command_set: -thread-select 6
      gdb.mi/mi1-pthreads.exp: check mi_thread_command_set: -thread-select 4
      gdb.mi/mi1-pthreads.exp: check mi_thread_command_set: -thread-select 5
      gdb.mi/mi1-pthreads.exp: check mi_thread_command_set: -thread-select 6
        PASS -> blank
        blank -> PASS

        Fluctuation with unknown cause.  Probably harmless.

    . gdb.mi/mi2-*.exp: *
        blank -> ERROR
        blank -> WARNING
        blank -> NOTE
        blank -> PASS
        blank -> FAIL
        blank -> UNRESOLVED

        Andrew C wrote some new tests which revealed a new crash in gdb.
        Good tests, bad gdb.  :)

    . gdb.objc/basicclass.exp: successfully compiled objc with posix threads test case
        PASS -> UNRESOLVED

        This is a cascade error from tcl errors in the previous file,
        gdb.mi2/mi2-watch.exp.

    . gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily

        Same analysis as gdb 5.3.

    . gdb.threads/linux-dp.exp: philosopher is distinct: 6
      gdb.threads/linux-dp.exp: philosopher is distinct: 7
        PASS -> FAIL
        FAIL -> PASS

        These tests are sensitive to a backtrace bug in gdb.  If a
        thread is waiting on 'select', then gdb prints a deficient
        backtrace, and the test FAILs.

          http://sources.redhat.com/gdb/bugs/1255
          [regression] bad backtrace for libc function 'sleep'

    . gdb.threads/pthreads.exp: check backtrace from thread 2
        FAIL -> PASS

        A multi-threaded inferior program tickles a known bug in
        backtracing.  The bug is deterministic, but the times when it
        happens is not.

          pr gdb/1255: [regression] bad backtrace for libc function 'sleep'
          http://sources.redhat.com/gdb/bugs/1255

    . gdb.threads/schedlock.exp: *
        PASS
        FAIL
      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 almost all configurations except for the
        "thread N ran" tests.  Here are the counts per thread.

                    PASS  FAIL
          thread 0     2    32
          thread 1    30     4
          thread 2    32     2
          thread 3    33     1
          thread 4    33     1
          thread 5    34     0

        One configuration had anomalous results with many FAILs:

          # gdb.log excerpt
          # target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0
          # gdb=gdb_6_0-branch 2003-08-07 20:31:55 UTC
          # gcc=gcc-3_3-branch 2003-08-06 22:13:13 UTC
          # binutils=2.13.90.0.2-2-rh
          # gformat=stabs+, glevel=2

          (gdb) break 41 if arg != 5
          Breakpoint 3 at 0x80484e5: file /berman/fsf/_today_/source/gdb/gdb_6_0-branch/src/gdb/testsuite/gdb.threads/schedlock.c, line 41.
          (gdb) continue
          Continuing.
          
          Program received signal SIGINT, Interrupt.
          [Switching to Thread 24580 (LWP 29837)]
          0x42028c82 in sigprocmask () from /lib/i686/libc.so.6
          (gdb) FAIL: gdb.threads/schedlock.exp: continue to breakpoint: return to loop (initial)
          ... many more FAILs ...

        I am throwing this on the 'unexplained mysteries' pile.

  . gdb HEAD

    checkout date is '2003-08-07 20:28:13 UTC'
    previous date is '2003-08-03 05:21:09 UTC'

    . gdb.base/annota3.exp: annotate ignore count change (pattern 5)
        FAIL -> PASS
        PASS -> FAIL

        The 'annotate ignore count change' test FAILed in 4
        configurations out of 34 tested.

        I have not analyzed this yet.

    . gdb.base/completion.exp: cd to ${objdir}
      gdb.base/completion.exp: complete 'file ./Make'
        PASS -> blank

        Same analysis as gdb gdb_6_0-branch.

    . gdb.base/corefile.exp: backtrace in corefile.exp
      gdb.base/corefile.exp: print func2::coremaker_local
        FAIL -> PASS
      gdb.base/gdb1250.exp: backtrace from abort
        KFAIL -> PASS

        Same analysis as gdb gdb_6_0-branch.

    . gdb.c++/annota2.exp: annotate-quit
      gdb.c++/annota3.exp: annotate-quit

        Same analysis as gdb 5.3.

    . gdb.mi/mi-pthreads.exp: check mi_thread_command_set: -thread-select 3
      gdb.mi/mi-pthreads.exp: check mi_thread_command_set: -thread-select 4
      gdb.mi/mi-pthreads.exp: check mi_thread_command_set: -thread-select 5
      gdb.mi/mi-pthreads.exp: check mi_thread_command_set: -thread-select 6
      gdb.mi/mi1-pthreads.exp: check mi_thread_command_set: -thread-select 6
        PASS -> blank
        blank -> PASS

        Same analysis as gdb gdb_6_0-branch.

    . gdb.mi/mi2-*.exp: *
        blank -> ERROR
        blank -> WARNING
        blank -> NOTE
        blank -> PASS
        blank -> FAIL
        blank -> UNRESOLVED

        Same analysis as gdb gdb_6_0-branch.

    . gdb.objc/basicclass.exp: successfully compiled objc with posix threads test case
        PASS -> UNRESOLVED

        Same analysis as gdb gdb_6_0-branch.

    . gdb.threads/linux-dp.exp: philosopher is distinct: 3
      gdb.threads/linux-dp.exp: philosopher is distinct: 4
      gdb.threads/linux-dp.exp: philosopher is distinct: 6
      gdb.threads/linux-dp.exp: philosopher is distinct: 7
        FAIL -> PASS
        PASS -> FAIL

        Same analysis as gdb gdb_6_0-branch.

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

        Fluctuation with unknown cause.  Probably harmless.

    . gdb.threads/pthreads.exp: check backtrace from thread 2
        FAIL -> PASS

        Same analysis as gdb gdb_6_0-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     3    31
          thread 1    32     2
          thread 2    34     0
          thread 3    33     1
          thread 4    33     1
          thread 5    34     0


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