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-24


. Highlights of This Spin

  All is calm.

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

. Old Bugs Fixed

  . gdb HEAD

    http://sources.redhat.com/gdb/bugs/1489
    GDB crashes executing breakpoint commands that continue the inferior

      Jim B fixed a bug in gdb.

. New Bugs Detected

  None.

. PR Count

  Query executed 2003-12-24 20:50:52 UTC

  1493 matches found
    22 analyzed
   673 closed
    23 feedback
   761 open
     3 paperwork
    11 suspended
  1493 TOTAL

. Libiberty Testing

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

. Gdb Testing

  My tables are at

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

  The previous tables are at

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

  . Non-PASS Results

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

  . gdb 6.0

    . gdb.cp/annota2.exp: annotate-quit
        KFAIL -> PASS
      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.mi/mi*-pthreads.exp: check mi_thread_command_set: -thread-select [3456]
        PASS -> blank
        blank -> PASS

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

  . gdb HEAD

    checkout date is '2003-12-24 07:13:44 UTC'
    previous date is '2003-12-16 20:03:39 UTC'

    . gdb.base/freebpcmd.exp: run program with breakpoint commands
        FAIL -> PASS

      Jim B fixed a bug in gdb.

        http://sources.redhat.com/gdb/bugs/1489
        GDB crashes executing breakpoint commands that continue the inferior

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

        Same analysis as gdb 6.0.

    . 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: *
        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    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        => 6.0, HEAD
  gcc        => 2.95.3, 3.2-7-rh, 3.3.2, gcc-3_3-branch, HEAD
  as         => 2.13.90.0.2-rh, 2.14, HEAD
  ld         => 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 * 3 * (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', 'as', 'ld', 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.
  as/ld are always matched.
  The vendor gcc is available only with vendor as/ld.
  The vendor gcc is available only with vendor binutils,
    thus the '(4*3+1*1)' term for gcc/as/ld 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.5
    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.8.tar.gz
    ftp://ftp.shout.net/pub/users/mec/migbat/migbat-0.8.tar.gz

. Test Bed Changes Since Last Report

  I split "binutils" into separate "as" and "ld".  This is needed for
  targets such as native hppa2.0w-hp-hpux11.11, which use the binutils
  version of "as" and the vendor version of "ld".

  I upgraded tcl from 8.4.4 to 8.4.5.

  I added support for native hppa2.0w-hp-hpux11.11 to migchain.

  I released migchain 0.8 and migbat 0.8.


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