sunday project, gdb, 2002-12-03

[Michael Elizabeth Chastain <mec at shout dot net>]

Highlights of this report:

. No new bugs from 2002-11-25 to 2002-12-03.

. I did a comparison of gdb 5.2 versus 5.2.91 and found 10 results
  which regressed.  In my opinion all of them are acceptable for a release.
  Full report published separately.
  
. gcc HEAD still has a lot of FAILs on c++ stabs+ debugging.  Look at
  "compare by gcc version" table for gdb=HEAD, gcc=.*, binutils=2.13.1,
  gformat=stabs+.

My tables are here:

  http://www.shout.net/~mec/sunday/2002-12-03/index.html

Michael C

. Summary

  . Test Matrix

    . Matrix

      target    => native
      host      => i686-pc-linux-gnu%rh-8
      gdb       => 5.2.1, 5.2.91, gdb_5_3-branch%20021203, HEAD%20021203
      gcc       => 2.95.3, 3.0.4, 3.1, 3.1.1, 3.2, 3.2.1, 3.2-7-rh, gcc-3_2-branch%20021203, HEAD%20021203
      binutils  => 2.13.90.0.2-rh, 2.13.1, binutils-2_13-branch%20021203, HEAD%20021203
      glibc     => 2.2.93-5-rh
      gformat   => dwarf-2, stabs+
      count        264 = *(1 1 4 +(*(8 4) 1) 1 2)

    . Notes

      target and host names are gnu triples with extra information after
      a '%' delimiter.

      versions which start with a number are official releases or snapshots.
      versions which start with a number and end with "-rh" are the
        vendor-supplied versions on my red hat linux host.
      versions named "HEAD" are the cvs HEAD.
      versions with any other name are cvs branches.
      cvs versions show the checkout date after a '%' delimiter.

    . libiberty

      Not tested yet (I need to update my test script).

    . gdb

      . Tables

        . http://www.shout.net/~mec/sunday/2002-12-03/index.html

      . Overview

        gdb 5.2.1:           0 build aborts, 0 test aborts, 512 attention lines
        gdb 5.2.91:          0 build aborts, 0 test aborts, 397 attention lines
        gdb gdb_5_3-branch:  0 build aborts, 0 test aborts, 390 attention lines
        gdb HEAD:            0 build aborts, 0 test aborts, 383 attention lines

        An attention line is a test with an attention results in one or
        more configurations.

        An attention result is any result except PASS.  This includes
        ERROR, WARNING, FAIL, KPASS, KFAIL, XPASS, XFAIL, UNRESOLVED,
        UNTESTED, UNSUPPORTED, and unknown results.

      . Old bugs fixed

        In gdb_5_3-branch and HEAD, gdb.threads/killed.exp improved
        on one test.

      . New bugs detected

        None.

. Test protocol changes since last report.

  I added gdb 5.2.91.

  I dropped binutils 2.11.2, 2.12, 2.12.1, and 2.13.

. Baseline software

  . host i686-pc-linux-gnu%rh-8

    make 3.79.1
    binutils 2.13.1
    gcc 2.95.3
    flex 2.5.4
    bison 1.35
    tcl 8.3.4
    expect 5.33.0
    dejagnu 1.4.2 + FernandoN kfail patch.

    The baseline software is used to build all the other software.
    It is not part of the test matrix.

    I will be upgrading the baseline software as time becomes available,
    starting with dejagnu 1.4.3, which has KFAIL support integrated.

. Analysis

  . libiberty

    . results

      . target native

        . host i686-pc-linux-gnu%rh-8

          No results available yet.

  . gdb

    The last report was 2002-11-25:

      http://www.shout.net/~mec/sunday/2002-11-25/Analysis.txt

    . 5.2.1

      . gdb.c++/annota2.exp: annotate quit
          pr gdb/544: gdb.c++/annota2.exp: annotate-quit test sometimes fails
          http://sources/redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=544
          Fluctuation in test result from unknown causes.

    . 5.2.91

      This is the first report for 5.2.91, so there are no previous
      results for comparison.

    . gdb_5_3-branch

      . gdb.c++/annota2.exp: annotate quit
          pr gdb/544: gdb.c++/annota2.exp: annotate-quit test sometimes fails
          http://sources/redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=544
          Fluctuation in test result from unknown causes.

      . gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
          FAIL -> PASS
          Looks like a gdb improvement.

      . gdb.threads/print-threads.exp: Hit kill break, 11 (slow with kill ...)
          PASS -> (blank)
          Looks harmless.

      . gdb.threads/schedlock.exp: *
          This test script is useless in this branch until the "args"
          patch gets applied.

    . HEAD

      . gdb.c++/annota2.exp: annotate quit
          pr gdb/544: gdb.c++/annota2.exp: annotate-quit test sometimes fails
          http://sources/redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=544
          Fluctuation in test result from unknown causes.

      . gdb.mi/gdb669.exp: MI and console have same threads (try 2)
        gdb.mi/gdb669.exp: -thread_list_ids (try 2)
        gdb.mi/gdb669.exp: console and MI have same number of threads (try 2)
        gdb.mi/gdb669.exp: finding threads in MI output (try 2)
          FAIL -> PASS, (blank) -> PASS
          PASS -> FAIL, PASS -> (blank)
          Looks like multi-threading still has issues.  Most of the changes
          were positive but a few configurations had PASS -> FAIL regressions.

      . gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily
          FAIL -> PASS
          Looks like a gdb improvement.

      . gdb.threads/print-threads.exp: Hit kill break, 11 (slow with kill ...)
          PASS -> (blank)
          Looks harmless.

      . gdb.threads/pthreads.exp: stopped before calling common_routine 15 times
          PASS -> PASS
          Shared counter noise, this is harmless.

      . gdb.threads/schedlock.exp: *
          Both good and bad changes.  This test is still in a state
          where it's better to analyze the absolute results than to
          compare results from date to date.