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]

sunday project, gdb, 2003-07-23


Highlights of this report

. gcc gcc-3_3-branch continues to show no regressions versus gcc 3.3
  for gdb testing, native i686-pc-linux-gnu, -gdwarf-2 and -gstabs+.

. gdb has a partial fix for one of the backtrace bugs.

. gcc HEAD has a new bug with debug names of static functions.
  The bug is already fixed so the fix will show in the next report.

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, still broken for stabs+)

. New Bugs Detected

  http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11669
  [3.4 regression] Calling of static functions does not work (build of glibc broken)

. PR Count

  Query executed 2003-07-24T16:30:26Z

  1295 matches found
    19 analyzed
   580 closed
    23 feedback
   659 open
     3 paperwork
    11 suspended
  1295 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-07-23/index.html

  The previous tables are at

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

  . Non-PASS Results

    gdb 5.3:             0 test aborts, 343 non-PASS results
    gdb gdb_6_0-branch:  0 test aborts, 303 non-PASS results
    gdb HEAD:            0 test aborts, 370 non-PASS results

  . 5.3

    . gdb.base/structs2.exp: structs2 breakpoint set
      gdb.base/structs2.exp: structs2 continue1
      gdb.base/structs2.exp: structs2 continue2
      gdb.base/structs2.exp: structs2 continue2: the program is no longer running
        PASS -> FAIL
        PASS -> blank
        blank -> FAIL

        This happened with gcc HEAD -gstabs+.

          http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11669
          [3.4 regression] Calling of static functions does not work (build of glibc broken)

        gcc HEAD regressed between 2003-07-19 and 2003-07-22.
        It generates names such as "foo.0" for static functions at file scope.

        The error messages refer to PRMS 13536, although PRMS is long gone.

        Geoff K has already fixed this bug, so the fix ought to show
        up in the next spin.

    . 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-07-23 19:06:22 UTC'
    previous date is '2003-07-18 19:59:53 UTC'

    . gdb.base/corefile.exp: backtrace in corefile.exp
        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 v3 -gdwarf-2 is fixed, but gcc v3 -gstabs+ is still broken.

    . gdb.base/structs2.exp: structs2 breakpoint set
      gdb.base/structs2.exp: structs2 continue1
      gdb.base/structs2.exp: structs2 continue2
      gdb.base/structs2.exp: structs2 continue2: the program is no longer running
        PASS -> FAIL
        PASS -> blank
        blank -> FAIL

        Same analysis as 5.3.

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

        Same analysis as 5.3.

    . gdb.threads/linux-dp.exp: philosopher is distinct: 6
      gdb.threads/linux-dp.exp: philosopher is distinct: 7
        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.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 3
      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
        blank -> PASS
        PASS -> blank

        Fluctuation with unknown cause.  Probably harmless.

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

        Same analysis as gdb 5.3.

    . gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (slow with kill breakpooint)
        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    10    24
          thread 1    23    11
          thread 2    30     4
          thread 3    28     6
          thread 4    32     2
          thread 5    34     0

  . gdb HEAD

    checkout date is '2003-07-23 19:03:31 UTC'
    previous date is '2003-07-18 19:56:05 UTC'

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

        Same analysis as gdb_6_0-branch,

    . gdb.base/structs2.exp: structs2 breakpoint set
      gdb.base/structs2.exp: structs2 continue1
      gdb.base/structs2.exp: structs2 continue2
      gdb.base/structs2.exp: structs2 continue2: the program is no longer running
        PASS -> FAIL
        PASS -> blank
        blank -> FAIL

        Same analysis as 5.3.

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

        Same analysis as 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 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
        blank -> PASS
        PASS -> blank

        Same analysis as gdb_6_0-branch.

    . 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

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

      gdb.threads/tls.exp: *
        blank -> ERROR
        blank -> PASS
        blank -> FAIL
        blank -> KFAIL
        blank -> UNRESOLVED
        blank -> UNSUPPORTED

        Elena Z wrote a new test script for thread local storage.
        This script is still in development.

      gdb.threads/tls-shared.exp:*
        blank -> ERROR
        blank -> WARNING
        blank -> PASS
        blank -> FAIL
        blank -> UNRESOLVED
        blank -> UNSUPPORTED

        Elena Z wrote a new test script for thread local storage.
        This script is still in development.

. Test Matrix

  target     => native
  host       => i686-pc-linux-gnu
  osversion  => red-hat-8.0
  gdb        => 5.3, gdb_6_0-branch%20030723, HEAD%20030723
  gcc        => 2.95.3, 3.2-7-rh, 3.3, gcc-3_3-branch%20030722, HEAD%20030722
  binutils   => 2.13.90.0.2-rh, 2.14, binutils-2_14-branch%20030722, HEAD%20030722
  glibc      => 2.2.93-5-rh
  gformat    => dwarf-2, stabs+
  glevel     => 2
  count         102 = 1 * 1 * 1 * 3 * (4*4+1*1) * 1 * 2 * 1

  'target' and 'host' are gnu configuration triples.

  'osversion' is the host operating system name, which is additional
  information beyond 'host'.

  'gdb', 'gcc', 'binutils', and 'glibc' are version 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.
  cvs versions (head and branch) show the checkout date after a '%' delimiter.

  'gformat' is the debugging information format.
  'glevel' is the debugging level.

  'count' is the total number of configurations tested.
  The vendor gcc is available only with vendor binutils,
    thus the '(4*4+1*1)' term for gcc/binutils combinations.

. Host Software

  . host=i686-pc-linux-gnu, osversion=red-hat-8.0

    make 3.79.1
    binutils 2.14
    gcc 3.3
    flex 2.5.4
    bison 1.875
    tcl 8.4.3
    expect 5.38.0
    dejagnu 1.4.3

  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 Build and Test), and they are licensed under the
  GPL.

    ftp://ftp.shout.net/pub/users/mec/migchain/migchain-0.6.tar.gz
    ftp://ftp.shout.net/pub/users/mec/migbat/migbat-0.6.tar.gz

. Test Bed Changes Since Last Report

  None.


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