sunday project, gdb, 2003-01-04

Sun Jan 5 23:53:00 GMT 2003

Highlights of this report:

. no new bugs detected

. gdb gdb_5_3-branch is still dormant.

My tables are here:

  http://www.shout.net/~mec/sunday/2003-01-04/index.html

There was a lot of gdb activity on 2003-01-04.  I checked out gdb HEAD
between 2003-01-04T16:50:48Z and 2003-01-04T16:54:55Z (but my clock is not
NTP sync'ed, and I don't know if the cvs server's clock is NTP sync'ed,
so allow a couple of minutes for drift).

Michael C

. Old Bugs Fixed

  Daniel J fixed a TCL quoting problem in gdb.base/store.exp.

. New Bugs Detected

  None.

. Libiberty Testing

  All tests passed.

  . target=native, host=i686-pc-linux-gnu, osversion=red-hat-8.0, libc=2.2.93-5-rh
      binutils HEAD                             649 tests, 0 failures
      gcc 2.95.3, binutils HEAD                 All 616 tests passed
      gcc 3.2.1, binutils HEAD                  All 648 tests passed
      gcc gcc-3_2-branch, binutils 2.13.2.1     All 648 tests passed
      gcc gcc-3_2-branch, binutils HEAD         All 648 tests passed
      gcc gcc-3_2-branch, binutils vendor       All 648 tests passed
      gcc gcc-3_3-branch, binutils 2.13.2.1     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.13.2.1               649 tests, 0 failures
      gcc HEAD, binutils HEAD                   649 tests, 0 failures
      gcc HEAD, binutils vendor                 649 tests, 0 failures
      gdb HEAD                                  649 tests, 0 failures

. Gdb Testing

  My tables are at:

    http://www.shout.net/~mec/sunday/2003-01-04/index.html

  The previous report was 2002-12-31:

    http://www.shout.net/~mec/sunday/2002-12-31/Analysis.txt

  . Counts

    gdb 5.3:   0 build aborts, 0 test aborts, 396 non-PASS results
    gdb HEAD:  0 build aborts, 0 test aborts, 367 non-PASS results

    A non-PASS result is any result except PASS.  This includes
    ERROR, WARNING, NOTE, FAIL, KPASS, KFAIL, XPASS, XFAIL, UNRESOLVED,
    UNTESTED, UNSUPPORTED, and unknown results.

  . 5.3

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

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

	pr gdb/568: GDB confused by messily-exiting multi-threaded programs
	http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb&cmd=view&pr=568

	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/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-branch

    gdb gdb_5_3-branch has been dormant since the relaase.
    I will resume test coverage when the branch becomes active.

  . HEAD

    . gdb.base/psymtab.exp: Don't search past end of psymtab.
	null -> PASS

	This is a new test.

    . gdb.base/store.exp: *
	ERROR -> null
	FAIL -> PASS
	UNRESOLVED -> PASS
	UNRESOLVED -> FAIL

	Daniel J fixed the TCL regular expressions in the test script.

    . gdb.c++/annota2.exp: annotate quit
      gdb.threads/killed.exp: GDB exits after multi-threaded program exits messily

	Same analysis as 5.3.

    . 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 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/mi1-pthreads.exp: check_mi_thread_command_set: -thread-select 6
	null -> FAIL

	This is a bug in the test script.  The test script selects a new
	thread and expects to see attributes including 'line' and 'file'.
	This FAILs if the new thread is blocked in a libc call and libc
	does not have symbols.

	A patch to fix this bug is waiting for review:

	  http://sources.redhat.com/ml/gdb-patches/...

      . gdb.threads/schedlock.exp: *

	  There are mixed changes, some good, some bad.  This test is still
	  in a state where it's better to analyze the absolute results
	  than to compare results from date to date.

. Test Matrix

  target    => native
  host      => i686-pc-linux-gnu
  osversion => red-hat-8.0
  gdb       => 5.3, HEAD%20030104
  gcc       => 2.95.3, 3.2-7-rh, 3.2.1, gcc-3_2-branch%20030104, gcc-3_3-branch%20030104, HEAD%20030104
  binutils  => 2.13.90.0.2-rh, 2.13.2.1, HEAD%20030104
  libc      => 2.2.93-5-rh
  gformat   => dwarf-2, stabs+
  count        64 = 1 * 1 * 1 * 2 * (5*3+1*1) * 1 * 2

  'target' and 'host' are gnu configuration triples.

  'osversion' is the host operating system name, which is additional
  information beyond 'host'.

  'gdb', 'gcc', 'binutils', and 'libc' 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.
  cvs versions (head and branch) show the checkout date after a '%' delimiter.

  'gformat' is the debugging information format.

  'count' is the total number of configurations tested.
  The vendor gcc is available only with vendor binutils,
    thus the '(5*3+1*1)' term for gcc/binutils combinations.

. Baseline Software

  . host=i686-pclinux-gnu, osversion=red-hat-8.0

    make 3.79.1
    binutils 2.13.2.1
    gcc 3.2.1
    flex 2.5.4
    bison 1.35
    tcl 8.4.1
    expect 5.38.0
    dejagnu 1.4.3

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

    The sources.redhat.com cvs repository has its own versions of
    tcl, expect, and dejagnu.  The sources.redhat.com versions behave
    differently than than the stock versions, especially in the area
    of regular expression quoting.  I don't have the resources to test
    with both tcl/expect/dejagnu stacks, so I choose the stock stack for
    my test bed.

. Test Bed Changes Since Last Report

  I upgraded baseline binutils to 2.13.2.1.
  I upgraded test matrix binutils to 2.13.2.1.

    URL: http://sources.redhat.com/ml/binutils/2003-01/msg00007.html

  Libiberty testing is back in town.