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-12-16


. Highlights of This Spin

  I dropped coverage of gdb gdb_6_0-branch.

  The demangler had a serious bug from 2003-11-29 to 2003-12-15 which
  hosed the C++ tests with gcc v3 -gstabs+.  I waited for this bug to be
  fixed before doing a spin.

  The current tables are always at:
    http://www.shout.net/~mec/sunday/current/index.html

. Old Bugs Fixed

  . libiberty

    Ian L-T fixed several more bugs in the demangler.

  . gdb HEAD

    http://sources.redhat.com/gdb/bugs/1377
    [regression] g++ 2.95.3, dwarf-2, hand function call: SIGSEGV
    http://sources.redhat.com/gdb/bugs/1465
    [regression] gdb prints bad object fields, gcc 2.95.3 -gdwarf-2

      Michael C fixed a bug in gdb.

    http://sources.redhat.com/gdb/bugs/1471
    [regression] ptype prints "int operator int();" with new demangler, stabs+

      Someone, probably David C, fixed a bug in gdb.

. New Bugs Detected

  None.

. PR Count

  Query executed 2003-12-17 16:31:50 UTC

  1486 matches found
    23 analyzed
   670 closed
    23 feedback
   756 open
     3 paperwork
    11 suspended
  1486 TOTAL

. Libiberty Testing

  . target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
      binutils HEAD                                      727 tests, 0 failures
      gcc 2.95.3, binutils HEAD                          All 616 tests passed
      gcc 3.3.2, 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                            727 tests, 0 failures
      gcc HEAD, binutils HEAD                            727 tests, 0 failures
      gcc HEAD, binutils vendor                          727 tests, 0 failures
      gdb HEAD                                           727 tests, 0 failures
      gdb carlton_dictionary-branch                      726 tests, 0 failures

    Ian L-T fixed more bugs and added more tests to the test suite.

    I know one outstanding issue with Java names that contain '$'
    characters.  Ian sent me a patch and it's waiting for me to review
    and test.

. Gdb Testing

  My tables are at

    http://www.shout.net/~mec/sunday/2003-12-16/index.html

  The previous tables are at

    http://www.shout.net/~mec/sunday/2003-11-30/index.html

  . Non-PASS Results

    gdb 6.0             318 non-PASS results
    gdb HEAD            410 non-PASS results

  . gdb 6.0

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

        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 thread_function breakpoint, 5 (slow with kill breakpoint)
        blank -> PASS

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

  . gdb HEAD

    checkout date is '2003-12-16 20:03:39 UTC'
    previous date is '2003-11-30 06:08:24 UTC'

    . gdb.base/break.exp: run until breakpoint set at small function, optimized file
        FAIL -> PASS

        gdb HEAD can optimize away calls to very small functions such as
        marker functions.  Fred F fixed the test script by moving the
        marker functions to a separate file.

    . gdb.base/break.exp: *
      gdb.base/completion.exp: *
      gdb.base/condbreak.exp: *
        PASS -> blank
        blank -> PASS
        XFAIL -> blank
        blank -> XFAIL

        Fred F improved the test scripts to use source file searches
        rather than source file line numbers.

    . gdb.base/freebpcmd.exp: set breakpoint
      gdb.base/freebpcmd.exp: send breakpoint commands
        blank -> PASS
      gdb.base/freebpcmd.exp: run program with breakpoint commands
        blank -> FAIL
      gdb.base/freebpcmd.exp: run program with breakpoint commands (GDB died)
        blank -> FAIL

        Jim B wrote a new test script.  The script detects an existing
        bug in gdb, so it should be changed to a KFAIL.

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

        Same analysis as gdb 6.0.

    . gdb.cp/class2.exp: print * aap at marker return 0
        KFAIL -> PASS
      gdb.cp/virtfunc.exp: print pBe->vvb()
      gdb.cp/virtfunc.exp: print pEe->fvb()
      gdb.cp/virtfunc.exp: print pEe->vvb()
        FAIL -> PASS

        Michael C fixed a bug in gdb.

          http://sources.redhat.com/gdb/bugs/1377
          [regression] g++ 2.95.3, dwarf-2, hand function call: SIGSEGV

          http://sources.redhat.com/gdb/bugs/1465
          [regression] gdb prints bad object fields, gcc 2.95.3 -gdwarf-2

    . gdb.cp/classes.exp: ptype class Foo (obsolescent gcc or gdb)
        PASS -> blank
      gdb.cp/classes.exp: ptype class Foo
        blank -> PASS

        Someone, probably David C, fixed a bug in gdb.

          http://sources.redhat.com/gdb/bugs/1471
          [regression] ptype prints "int operator int();" with new demangler, stabs+

        The test script accepted illegal output as PASS with
        "(obsolescent gcc or gdb)".  I filed a PR on the test script.

    . gdb.cp/rtti.exp: print *e2
        KFAIL -> KFAIL

        Michael C improved the test script from one KFAIL to a better
        KFAIL.

    . gdb.objc/nondebug.exp: break on non-debuggable method
        FAIL -> KFAIL

        Michael C improved the test script.

    . gdb.objc/objcdecode.exp: continue after break on multiply defined symbol
        FAIL -> KFAIL

        Michael C improved the test script.

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

. Test Matrix

  target     => native
  host       => i686-pc-linux-gnu
  osversion  => red-hat-8.0
  gdb        => 6.0, HEAD
  gcc        => 2.95.3, 3.2-7-rh, 3.3.2, 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         52 = 1 * 1 * 1 * 2 * (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.2
    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.7.tar.gz
    ftp://ftp.shout.net/pub/users/mec/migbat/migbat-0.7.tar.gz

. Test Bed Changes Since Last Report

  No externally visible changes.  I've made a lot of adjustments for the
  upcoming hppa2.0w-hp-hpux11.11 host.


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