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-03-15


Highlights of this report:

. two regressions detected in gcc HEAD from 2003-02-27 to 2003-03-15

. one regression detected in gdb HEAD from 2003-02-27 to 2003-03-15

My tables are here:

  http://www.shout.net/~mec/sunday/2003-03-15/index.html

Michael C

. Old Bugs Fixed

  . David C fixed pr gdb/33, "name matching on template names is
    sensitive to white space".

. New Bugs Detected

  . gcc HEAD dwarf-2 regressions, 2003-02-27 to 2003-03-15

      No PR yet.

      A C program fails to generate type definitions for:

	typedef char t_char_array[];
	typedef int (*func_type) (int (*) (int, float), float);

  . gcc HEAD stabs+ regressions, 2003-02-27 to 2003-03-08

      pr gcc/10055: [3.4 regression] gcc emits "<internal>" as source filename with -gstabs+
      http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gcc&cmd=view&pr=10055

      A c++ program has its source filename listed as '<internal>'
      rather than the actual filename.

  . gcc HEAD additional regressions

      I gave up analyzing gcc HEAD regressions and am dropping coverage
      of gcc HEAD.  I will pick up gcc HEAD again after pr gcc/10055 is
      fixed and after gdb 5.4/6.0 is released.

  . gdb HEAD regressions, 2003-02-27 to 2003-03-15

      No PR.

      gdb causes SIGFPE in target program with gcc 2.95.3.

      Andrew C has fixed this.

. PR Count

  Query executed 2003-03-24T19:52:00Z

  1149 matches found
    17 analyzed
   479 closed
    12 feedback
   629 open
     4 paperwork
     8 suspended
  1149 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-03-15/index.html

  The previous report was 2003-02-28:

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

  . Counts

    gdb 5.3:             0 test aborts, 390 non-PASS results
    gdb HEAD:            0 test aborts, 391 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.base/ptype.exp: ptype t_char_array
      gdb.base/ptype.exp: ptype func_type
	PASS -> FAIL

	No PR yet.

	gcc HEAD regressed between 2003-02-27 and 2003-03-14.
	This happened with gcc HEAD%20030314 -gdwarf-2 -g2.
	This did not happen with gcc HEAD%20030314 -gstabs+ -g2.

	gdb.log excerpts:

	  (gdb) ptype t_char_array
	  No symbol "t_char_array" in current context.
	  (gdb) FAIL: gdb.base/ptype.exp: ptype t_char_array

	  (gdb) ptype func_type
	  No symbol "func_type" in current context.
	  (gdb) FAIL: gdb.base/ptype.exp: ptype func_type

    . gdb.c++/annota2.exp: breakpoint main
	PASS -> FAIL
      gdb.c++/annota2.exp: breakpoint at main
	PASS -> null
      gdb.c++/annota2.exp: break at main
	null -> FAIL
      gdb.c++/anon-union.exp: next *
      gdb.c++/classes.exp: next to inheritance3
      gdb.c++/classes.exp: print (int)pmi == sizeof(int)
      gdb.c++/m-data.exp: continue to *
      gdb.c++/m-static.exp: continue to *
      gdb.c++/method.exp: break *
      gdb.c++/method.exp: continue to *
      gdb.c++/namespace.exp: break *
      gdb.c++/overload.exp: list overloaded function *
      gdb.c++/ovldbreak.exp: *
      gdb.c++/templates.exp: break *
      gdb.c++/templates.exp: * breakpoint *
      gdb.c++/try_catch.exp: continue to *
	PASS -> FAIL
	PASS -> XFAIL
	PASS -> null
	null -> FAIL
	null -> XFAIL

	pr gcc/10055: [3.4 regression] gcc emits "<internal>" as source filename with -gstabs+
	http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gcc&cmd=view&pr=10055

	gcc HEAD regressed between 2003-02-27 and 2003-03-15.
	This happened with gcc HEAD%20030315 -gstabs+ -g2.

	gdb.log excerpt:

	  (gdb) break 25
	  Breakpoint 1 at 0x80483c1: file <internal>, line 25.
	  (gdb) FAIL: gdb.c++/annota2.exp: breakpoint main

    . 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.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-03-15 19:56:35 UTC'

    . gdb.base/ptype.exp: ptype t_char_array
      gdb.base/ptype.exp: ptype func_type
	PASS -> FAIL

	Same analysis as 5.3.

    . gdb.base/return2.exp: *

        gdb causes a SIGFPE in the target program.  This happens with
	gcc 2.95.3, but does not happen with gcc 3.X.

	  # gdb.log excerpt
	  break float_func
	  Breakpoint 8 at 0x804845b: file /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/return2.c, line 57.
	  (gdb) PASS: gdb.base/return2.exp: set break on float_func
	  continue
	  Continuing.
	  
	  Program received signal SIGFPE, Arithmetic exception.
	  0x080484e4 in main (argc=1, argv=0xbffff7f4) at /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base/return2.c:104
	  104	  testval.float_testval = 2.7182818284590452354;/* long_long_checkpoint */
	  (gdb) FAIL: gdb.base/return2.exp: continue to float_func

	Mark K analyzed this:

	  http://sources.redhat.com/ml/gdb-patches/2003-03/msg00340.html

	Andrew C committed a patch to fix this:

	  http://sources.redhat.com/ml/gdb-patches/2003-03/msg00352.html

	This patch works for me.

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

	Same analysis as 5.3.

    . gdb.c++/annota2.exp: breakpoint main
	PASS -> FAIL
      gdb.c++/annota2.exp: breakpoint at main
	PASS -> null
      gdb.c++/annota2.exp: break at main
	null -> FAIL
      gdb.c++/anon-union.exp: next *
      gdb.c++/classes.exp: next to inheritance3
      gdb.c++/classes.exp: print (int)pmi == sizeof(int)
      gdb.c++/m-data.exp: continue to *
      gdb.c++/m-static.exp: continue to *
      gdb.c++/method.exp: break *
      gdb.c++/method.exp: continue to *
      gdb.c++/namespace.exp: break *
      gdb.c++/overload.exp: list overloaded function *
      gdb.c++/ovldbreak.exp: *
      gdb.c++/templates.exp: break *
      gdb.c++/templates.exp: * breakpoint *
      gdb.c++/try_catch.exp: continue to *
	PASS -> FAIL
	PASS -> XFAIL
	PASS -> null
	null -> FAIL
	null -> XFAIL

	Same analysis as 5.3.

    . gdb.c++/casts.exp: break 19
	null -> FAIL
      gdb.c++/casts.exp: *
	PASS -> FAIL
	null -> FAIL

	This happens with gcc HEAD%20030314 -stabs+.

	  # gdb.log excerpt
	  (gdb) search casts.exp: 1
	  19	  return 0;  /* breakpoint spot: casts.exp: 1 */
	  (gdb) break 19
	  No line 19 in file "/berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.c++/casts.cc".
	  (gdb) FAIL: gdb.c++/casts.exp: break 19
	  run
	  Starting program: /berman/fsf/_today_/berman/test/gdb.c++/casts 
	  
	  Program exited normally.
	  (gdb) FAIL: gdb.c++/casts.exp: run

	This is a regression from gcc HEAD%20030227.

    . gdb.c++/classes.exp: print ('ClassWithEnum::PrivEnum') 42
	null -> KFAIL
	null -> PASS
      gdb.c++/classes.exp: print (ClassWithEnum::PrivEnum) 42
	XFAIL -> FAIL
	XPASS -> PASS
      gdb.c++/classes.exp: ptype obj_with_enum
	XFAIL -> KFAIL
	XFAIL -> FAIL

	David C improved the test script.

    . gdb.c++/m-data.exp: *
	PASS -> FAIL
	NULL -> FAIL

	  New regressions with gcc HEAD.

    . gdb.c++/m-static.exp: *
	PASS -> FAIL
	NULL -> FAIL

	  New regressions with gcc HEAD.

    . gdb.c++/pr-1023.exp: break *
	PASS -> FAIL

	  New regressions with gcc HEAD.

    . gdb.c++/pr-574.exp: *
	PASS -> FAIL
	null -> FAIL

	  New regressions with gcc HEAD.

    . gdb.c++/printmethod.exp: *
	PASS -> FAIL
	null -> FAIL

	  New regressions with gcc HEAD.

    . gdb.c++/psmang.exp: break *
	PASS -> FAIL

	  New regressions with gcc HEAD.

    . gdb.c++/templates.exp: *
	PASS -> FAIL
	PASS -> null
	null -> FAIL

	  New regressions with gcc HEAD.

    . gdb.c++/templates.exp: print Foo<volatile char *>::foo
	KFAIL -> PASS

	David C fixed PR gdb/33 in gdb.

    . gdb.c++/templates.exp: constructor breakpoint
	FAIL -> KFAIL
      gdb.c++/templates.exp: destructor breakpoint
	FAIL -> KFAIL
      gdb.c++/templates.exp: print Garply<Garply<char> >::garply
	FAIL -> PASS
      gdb.c++/templates.exp: ptype Bar
	KFAIL -> PASS
      gdb.c++/templates.exp: ptype Baz
	KFAIL -> PASS
      gdb.c++/templates.exp: ptype Foo
	KFAIL -> PASS
      gdb.c++/templates.exp: ptype Qux
	KFAIL -> PASS
      gdb.c++/templates.exp: ptype 
	KFAIL -> PASS
      gdb.c++/templates.exp: ptype T5<int>
	FAIL -> KFAIL
      gdb.c++/templates.exp: ptype t5i
	FAIL -> null

	David C improved the test script.

    . gdb.c++/try_catch.exp: continue to breakpoint: *
	PASS -> FAIL
      gdb.c++/try_catch.exp: setting breakpoint at *
	null -> FAIL

	  New regressions with gcc HEAD.

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

	Same analysis as 5.3.

    . gdb.threads/schedlock.exp: *

	Still crazy after all these years.

	This test is still in a state where it's better to analyze the
	absolute results than to compare results from date to date.


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