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]

gdb, native i686-pc-linux-gnu


. Highlights of This Spin

  I added gdb carlton_dictionary-branch and gdb drow-cplus-branch.
  I have data tables for these, but not much analysis to offer.
  drow-cplus-branch has a problem with gcc 2.95.3 -gstabs+.

  I added gcc gcc-3_4-branch.  The results for gcc gcc-3_4-branch are
  substantially the same as gcc HEAD.

  Speaking of gcc branches, gcc gcc-3_3-branch continues to show no
  debug regressions compared to gcc 3.3.2 on native i686-pc-linux-gnu,
  with dwarf-2 and stabs+.

. Old Bugs Fixed

  . gcc HEAD

    gcc HEAD improved its line number output, fixing several regressions
    from gcc 3.3.2.  These improvements are also in gcc gcc-3_4-branch.

. New Bugs Detected

  None.

. PR Count

  Query executed 2004-01-21 08:25:41 UTC

  1531 matches found
    22 analyzed
   697 closed
    28 feedback
   768 open
     3 paperwork
    13 suspended
  1531 TOTAL

. Libiberty Testing

  . target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
      binutils HEAD                  742 tests, 0 failures
      gcc gcc-3_3-branch             649 tests, 0 failures
      gcc gcc-3_4-branch             742 tests, 0 failures
      gcc HEAD                       742 tests, 0 failures
      gdb HEAD                       742 tests, 0 failures
      gdb carlton_dictionary-branch  726 tests, 0 failures
      gdb drow-cplus-branch          742 tests, 0 failures

    For gcc tests, the test results are with binutils 2.14.
    The binutils version should not make a difference.

. Gdb Testing

  My tables are at

    http://www.shout.net/~mec/sunday/2004-01-19/index.html

  The previous tables are at

    http://www.shout.net/~mec/sunday/2004-01-18/index.html

  . Non-Pass Results

    gdb 6.0                        353 non-PASS results
    gdb HEAD                       433 non-PASS results
    gdb carlton_dictionary-branch  463 non-PASS results
    gdb drow-cplus-branch          653 non-PASS results

  . gdb 6.0

    . gdb.base/annota1.exp: send SIGUSR1
        FAIL -> PASS
      gdb.base/annota3.exp: send SIGUSR1
      gdb.base/annota3.exp: backtrace @ signal handler
        FAIL -> PASS
      gdb.base/break.exp: breakpoint at start of multi line while conditional
      gdb.base/break.exp: breakpoint info
        PASS -> FAIL
      gdb.base/break.exp: run until function breakpoint, optimized file
        PASS -> blank
      gdb.base/break.exp: run until function breakpoint, optimized file (code motion)
        blank -> PASS
      gdb.base/condbreak.exp: run until breakpoint at marker1
      gdb.base/condbreak.exp: run until breakpoint at marker2
        XFAIL -> PASS
      gdb.base/ena-dis-br.exp: continue to break marker1
      gdb.base/ena-dis-br.exp: continue to auto-disabled break marker2
      gdb.base/ena-dis-br.exp: continue to break marker1, 2nd time
        XFAIL -> PASS
      gdb.base/funcargs.exp: run to call5a
      gdb.base/funcargs.exp: print st
      gdb.base/funcargs.exp: continue to call6k
      gdb.base/funcargs.exp: run to hitbottom
        FAIL -> PASS
      gdb.base/watchpoint.exp: run to marker1 in test_simple_watchpoint
      gdb.base/watchpoint.exp: watchpoints found in watchpoint/breakpoint table
      gdb.base/watchpoint.exp: run to marker1 in test_disabling_watchpoints
        FAIL -> PASS
      gdb.base/watchpoint.exp: *
        blank -> PASS
      gdb.cp/m-data.exp: continue to breakpoint: continue to shadow breakpoint
        FAIL -> PASS
      gdb.cp/ovldbreak.exp: continue to bp overloaded: char
      gdb.cp/ovldbreak.exp: continue to bp overloaded: signed char
      gdb.cp/ovldbreak.exp: continue to bp overloaded: unsigned char
      gdb.cp/ovldbreak.exp: continue to bp overloaded: short
      gdb.cp/ovldbreak.exp: continue to bp overloaded: unsigned short
      gdb.cp/ovldbreak.exp: continue to bp overloaded: double
        KFAIL -> PASS
      gdb.trace/packetlen.exp: run trace experiment
        FAIL -> PASS

        gcc HEAD improved its line number output.  Besides printing
        better line numbers, this improves the values shown for
        arguments at the start of a function, specifically 'char',
        'short', and 'double' values.

        This fixes PR gdb/1025 with gcc HEAD, but the problem still
        happens with gcc 2.95.3 -gdwarf-2.

          http://sources.redhat.com/gdb/bugs/1025
          failures in gdb.c++/ovldbreak.exp

        Two tests in break.exp regressed.  This is probably harmless,
        but could use investigation.

    . 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]
        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/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    27
          thread 1    29     3
          thread 2    30     2
          thread 3    31     1
          thread 4    32     0
          thread 5    32     0

  . gdb HEAD

    checkout date is '2004-01-19 20:58:13 UTC'
    previous date is '2004-01-18 04:33:29 UTC'

    . gdb.base/annota1.exp: send SIGUSR1
        FAIL -> PASS
      gdb.base/annota3.exp: send SIGUSR1
      gdb.base/annota3.exp: backtrace @ signal handler
        FAIL -> PASS
      gdb.base/break.exp: breakpoint at start of multi line while conditional
      gdb.base/break.exp: breakpoint info
        PASS -> FAIL
      gdb.base/break.exp: run until function breakpoint, optimized file
        PASS -> blank
      gdb.base/break.exp: run until function breakpoint, optimized file (code motion)
        blank -> PASS
      gdb.base/condbreak.exp: run until breakpoint at marker1
      gdb.base/condbreak.exp: run until breakpoint at marker2
        XFAIL -> PASS
      gdb.base/ena-dis-br.exp: continue to break marker1
      gdb.base/ena-dis-br.exp: continue to auto-disabled break marker2
      gdb.base/ena-dis-br.exp: continue to break marker1, 2nd time
        XFAIL -> PASS
      gdb.base/funcargs.exp: run to call5a
      gdb.base/funcargs.exp: print st
      gdb.base/funcargs.exp: continue to call6k
      gdb.base/funcargs.exp: run to hitbottom
        FAIL -> PASS
      gdb.base/sepdebug.exp: breakpoint at start of multi line while conditional
      gdb.base/sepdebug.exp: breakpoint into
        PASS -> FAIL
      gdb.base/watchpoint.exp: run to marker1 in test_simple_watchpoint
      gdb.base/watchpoint.exp: watchpoints found in watchpoint/breakpoint table
      gdb.base/watchpoint.exp: run to marker1 in test_disabling_watchpoints
        FAIL -> PASS
      gdb.base/watchpoint.exp: *
        blank -> PASS
      gdb.cp/m-data.exp: continue to breakpoint: continue to shadow breakpoint
        FAIL -> PASS
      gdb.cp/ovldbreak.exp: continue to bp overloaded: char
      gdb.cp/ovldbreak.exp: continue to bp overloaded: signed char
      gdb.cp/ovldbreak.exp: continue to bp overloaded: unsigned char
      gdb.cp/ovldbreak.exp: continue to bp overloaded: short
      gdb.cp/ovldbreak.exp: continue to bp overloaded: unsigned short
      gdb.cp/ovldbreak.exp: continue to bp overloaded: double
        KFAIL -> PASS
      gdb.trace/packetlen.exp: run trace experiment
        FAIL -> PASS

        Same analysis as gdb 6.0.

        Two tests in break.exp and two tests in sepdebug.exp regressed.
        This is probably harmless, but could use investigation.

    . gdb.base/gdb1476.exp: Memory at address 0 is possibly executable
        UNTESTED -> blank
        UNRESOLVED -> blank
      gdb.base/gdb1476.exp: continue to null pointer call
        blank -> PASS
        blank -> UNRESOLVED
      gdb.base/gdb1476.exp: backtrace from null pointer call
        blank -> PASS

        Mark K improved the test script.

        The UNRESOLVED results are a cascade problem from an ERROR from
        the previous test script, gdb1250.exp.  gdb is working fine.

    . 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.cp/local.exp: ptype InnerLocal::NestedInnerLocal
        FAIL -> PASS

        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    29
          thread 1    29     3
          thread 2    31     1
          thread 3    31     1
          thread 4    31     1
          thread 5    32     0

  . gdb carlton_dictionary-branch
  . gdb drow-cplus-branch

    carlton_dictionary-branch  checkout date is '2004-01-19 21:00:35 UTC'
    drow-cplus-branch          checkout date is '2004-01-19 21:03:25 UTC'

    This is the first spin with gdb carlton_dictionary-branch and
    drow-cplus-branch, so I have no comparison with a previous spin.

    The counts table points out that drow-cplus-branch has 91 ERROR
    and 9 WARNING with gcc 2.95.3 -gstabs+.

    The compare-by-gdb tables have some useful data, but there is a lot
    of noise from the differences between gdb test suite 6.0 and the
    other versions of gdb test suite.

. Test Matrix

  target     => native
  host       => i686-pc-linux-gnu
  osversion  => red-hat-8.0
  gdb        => 6.0, HEAD, carlton_dictionay-branch, drow-cplus-branch
  cc         => gcc 2.95.3, gcc 3.2-7-rh, gcc 3.3.2, gcc gcc-3_3-branch, gcc gcc-3_4-branch, gcc HEAD
  as         => binutils 2.13.90.0.2-rh, binutils 2.14, binutils HEAD
  ld         => binutils 2.13.90.0.2-rh, binutils 2.14, binutils HEAD
  libc       => glibc 2.2.93-5-rh
  gformat    => dwarf-2, stabs+
  glevel     => 2
  count         84 = 1 * 1 * 1 * (2*(5*3+1*1) + 2*(5*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' is a version name.

  'cc', 'as', 'ld', and 'libc' are package 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 '(5*3+1*1)' term for cc/as/ld combinations.

  gdb carlton_dictionary_branch and gdb drow-cplus-branch are tested
  only with binutils 2.14, thus the term '5*1' for their cc/as/ld
  combinations.

. Package Versions

  binutils  HEAD                       2004-01-19 06:08:35 UTC
  gcc       HEAD                       2004-01-19 06:29:00 UTC
  gcc       gcc-3_3-branch             2004-01-19 06:36:23 UTC
  gcc       gcc-3_4-branch             2004-01-19 06:41:21 UTC
  gdb       HEAD                       2004-01-19 20:58:13 UTC
  gdb       carlton_dictionary-branch  2004-01-19 21:00:35 UTC
  gdb       drow-cplus-branch          2004-01-19 21:03:25 UTC

. 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 added gcc gcc-3_4-branch.
  I added gdb carlton_dictionary-branch.
  I added gdb drow-cplus branch.


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