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-04-09


My tables are here:

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

Michael C

. Old Bugs Fixed

  . gcc HEAD

    . gdb.c++/inherit.exp: print g_vB
      gdb.c++/inherit.exp: print g_vC
      gdb.c++/inherit.exp: print g_vD

	gcc HEAD with -gstabs+ improved slightly in inherit.exp.

  . gdb HEAD

    . gdb.base/relocate.exp: *
	FAIL -> PASS
	FAIL -> null
	null -> PASS

	Someone fixed a bug in gdb.

    . gdb.mi/mi-cli.exp: Process no longer exists
      gdb.mi/mi-cli.exp: -interpreter-exec-console "set $pc=0x0"

	Andrew C fixed a bug in gdb.

. New Bugs Detected

  None.

. PR Count

  Query executed 2003-04-10T16:03:00Z

  1175 matches found
    18 analyzed
   492 closed
    15 feedback
   637 open
     4 paperwork
     9 suspended
  1175 TOTAL

. Libiberty Testing

  . 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.2, 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-04-09/index.html

  The previous report was 2003-04-02:

    http://www.shout.net/~mec/sunday/2003-04-02/Analysis.txt

  . Non-PASS Results

    gdb 5.3:             0 test aborts, 383 non-PASS results
    gdb HEAD:            0 test aborts, 390 non-PASS 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 probably due to a signal handling
        race in the command loop.

    . gdb.c++/inherit.exp: print g_vB
      gdb.c++/inherit.exp: print g_vC
      gdb.c++/inherit.exp: print g_vD
	FAIL -> PASS

	gcc improved.  This happened with gdb 5.3, gcc HEAD, -gstabs+.

    . 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

  . HEAD

    checkout date is '2003-04-10 00:52:36 UTC'

    . gdb.base/callfuncs.exp: call function causing a breakpoint and then do a return
      gdb.base/callfuncs.exp: call function causing a breakpoint then do a finish
	null -> PASS

	Andrew C wrote some new tests.

    . gdb.base/pointers.exp: continue to marker1
	null -> PASS

	Andrew C wrote a new test.

    . gdb.base/relocate.exp: *
	FAIL -> PASS
	FAIL -> null
	null -> PASS

	Someone fixed a bug in gdb.

    . gdb.c++/annota2.exp: annotate-quit

	Same analysis as 5.3.

    . gdb.c++/derivation.exp: re-selected 'main' frame after inferior call
      gdb.c++/overload.exp: re-selected 'main' frame after inferior call
      gdb.c++/userdef.exp: re-selected 'main' frame after inferior call
	null -> PASS

	Jim B wrote a new test.

    . gdb.c++/inherit.exp: print g_vB
      gdb.c++/inherit.exp: print g_vC
      gdb.c++/inherit.exp: print g_vD
	FAIL -> PASS

	gcc improved.  This happened with gdb 5.3, gcc HEAD, -gstabs+.

    . gdb.mi/mi-cli.exp: Process no longer exists
	ERROR -> null
      gdb.mi/mi-cli.exp: -interpreter-exec console "set $pc=0x0"
	UNRESOLVED -> PASS

	Andrew C fixed a bug in gdb.

    . gdb.mi/mi-file.exp: request path info of current source file (basics.c)
	null -> PASS

	Bob R wrote a new test.

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

	Same analysis as 5.3.

    . gdb.threads/schedlock.exp: *

        New date, same story.

	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%20030409
  gcc        => 2.95.3, 3.2-7-rh, 3.2.2, gcc-3_2-branch%20030408, gcc-3_3-branch%20030408, HEAD%20030408
  binutils   => 2.13.90.0.2-rh, 2.13.2.1, HEAD%20030408
  glibc      => 2.2.93-5-rh
  gformat    => dwarf-2, stabs+
  glevel     => 2
  count         64 = 1 * 1 * 1 * 2 * (5*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.
  cvs versions (head and branch) show the checkout date after a '%' delimiter.

  '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 '(5*3+1*1)' term for gcc/binutils combinations.

. Baseline software

  . host=i686-pc-linux-gnu, osversion=red-hat-8.0

    make 3.79.1
    binutils 2.13.2.1
    gcc 3.2.2
    flex 2.5.4
    bison 1.875
    tcl 8.4.1
    expect 5.38.0
    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 they are licensed under the GPL.

      ftp://ftp.shout.net/pub/users/mec/migchain/migchain-0.3.tar.gz

. Test Bed Changes Since Last Report

  None.


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