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-09-05


. Highlights of this report

  gdb 5.3.91 is okay.

  I found several new bugs in binutils HEAD and gcc HEAD.
  See 'New Bugs Detected' below.

Michael C

. Old Bugs Fixed

  None.

. New Bugs Detected

  . binutils HEAD

    binutils/gas upgraded to autoconf 2.57, and now it has an
    installation problem: the assembler installs as i686-pc-linux-gnu-as
    rather than as.  My test bed accommodates this.

  . gcc HEAD

    gcc HEAD had a garbage collection bug for several days,
    pr gcc/12161.  Geoff K fixed it.

    http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12204
    [regression] gcc emits bogus .file when __inline__ called

. PR Count

  Query executed 2003-09-10T18:34:14Z

  1372 matches found
    22 analyzed
   614 closed
    27 feedback
   695 open
     3 paperwork
    11 suspended
  1372 TOTAL

. Libiberty Testing

  . target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
      binutils HEAD                                      714 tests, 31 failures
      gcc 2.95.3, binutils HEAD                          All 616 tests passed
      gcc 3.3.1, binutils HEAD                           649 tests, 0 failures
      gcc gcc-3_3-branch, binutils 2.14                  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 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-09-05/index.html

  The previous tables are at

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

  . Non-PASS Results

    gdb 5.3             424 non-PASS results
    gdb 5.3.91          441 non-PASS results
    gdb gdb_6_0-branch  444 non-PASS results
    gdb HEAD            483 non-PASS results

  . 5.3

    . 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/print-threads.exp: Hit kill breakpoint, 10 (slow with kill breakpoint)
        blank -> PASS

        Fluctuation with unknown cause.  Probably harmless.

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

    This is the first report for gdb 5.3.91.

    There were no significant differences between gdb gdb_6_0-branch
    2003-09-05 17:37:31 UTC and gdb 5.3.91.

  . gdb_6_0-branch

    current  date is '2003-09-05 17:37:31 UTC'
    previous date is '2003-08-28 16:20:10 UTC'

    . gdb.base/fileio.exp: *
        PASS -> FAIL

        This happened with gcc HEAD, all binutils, both dwarf-2 and
        stabs+.  This is a new bug in gcc HEAD.

          http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12204
          [regression] gcc emits bogus .file when __inline__ called

    . gdb.cp/annota2.exp: annotate-quit
      gdb.cp/annota3.exp: annotate-quit (pattern 1)

        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.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
      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/mi2-pthreads.exp: check mi_thread_command_set: -thread-select 6
        PASS -> blank
        blank -> PASS

        Fluctuation with unknown cause.  Probably harmless.

    . gdb.threads/print-threads.exp: Hit thread_function breakpoint, 5 (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     5    21
          thread 1    20     6
          thread 2    24     2
          thread 3    24     2
          thread 4    23     3
          thread 5    26     0

  . gdb HEAD

    checkout date is '2003-09-05 16:56:43 UTC'
    previous date is '2003-08-28 16:15:29 UTC'

    . gdb.base/fileio.exp: *
        PASS -> FAIL

        Same analysis as gdb gdb_6_0-branch.

    . gdb.base/gdb1250.exp: *
        PASS -> blank
        blank -> ERROR
        blank -> WARNING
        blank -> FAIL
        blank -> UNRESOLVED

        This happened with gcc HEAD, all binutils, both dwarf-2 and
        stabs+.  This is a change in gcc HEAD.

          http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12213
          [3.4 regression] warning: conflicting types for builtin-function 'gamma'

        It turns out that gcc HEAD is conforming to specifications.
        I committed a change to our test program.

    . gdb.base/gdbvars.exp: Set value-history[1] using $1
        PASS -> UNRESOLVED

        Cascade failure from gdb.base/gdb1250.exp.

    . gdb.base/relocate.exp: add-symbol-file relocate.o $offset
      gdb.base/relocate.exp: add-symbol-file relocate.o 0
        PASS -> FAIL
      gdb.stabs/weird.exp: weirdx.o read without error
        PASS -> blank
      gdb.stabs/weird.exp: Errors reading weirdx.o
        blank -> FAIL

        gdb prints a new message and the test script can't handle it.
        gdb.log excerpts:

          # old
          Reading symbols from /berman/fsf/_today_/berman/test/gdb.base/relocate.o...done.^M
          (gdb) PASS: gdb.base/relocate.exp: add-symbol-file relocate.o 0

          # new
          Reading symbols from /berman/fsf/_today_/berman/test/gdb.base/relocate.o...done.^M
          Using host libthread_db library "/lib/libthread_db.so.1".^M
          (gdb) FAIL: gdb.base/relocate.exp: add-symbol-file relocate.o 0

        Elena Z published a patch for relocate.exp.
        I tested the patch and it worked fine for me.

    . gdb.cp/annota2.exp: annotate-quit
      gdb.cp/annota3.exp: annotate-quit (pattern 1)

        Same analysis as gdb gdb_6_0-branch.

    . 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
      gdb.mi/mi2-pthreads.exp: check mi_thread_command_set: -thread-select 4
      gdb.mi/mi2-pthreads.exp: check mi_thread_command_set: -thread-select 5
      gdb.mi/mi2-pthreads.exp: check mi_thread_command_set: -thread-select 6
        PASS -> blank
        blank -> PASS

        Same analysis as gdb gdb_6_0-branch.

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

        Same analysis as gdb 5.3.

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

. Test Matrix

  target     => native
  host       => i686-pc-linux-gnu
  osversion  => red-hat-8.0
  gdb        => 5.3, 5.3.91, gdb_6_0-branch, HEAD
  gcc        => 2.95.3, 3.2-7-rh, 3.3.1, gcc-3_3-branch, HEAD
  binutils   => 2.13.90.0.2-rh, 2.14, HEAD
  glibc      => 2.2.93-5-rh
  gformat    => dwarf-2, stabs+
  glevel     => 2
  count         102 = 1 * 1 * 1 * 4 * (4*3+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.

  '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*3+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.4
    expect 5.39
    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 Gnu 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

  I added target gdb 5.3.91.

  I upgraded host tcl from 8.4.3 to 8.4.4.  There were no significant
  differences in the test results.

  I upgraded host expect from 5.38 to 5.39.  There were no significant
  differences in the test results.


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