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]

Sunday Project gdb test results, 2001-06-29


Here are my Sunday Project results for 2001-06-29.

The merged results for all platforms contain 17 ERRORs, 0 WARNINGs,
and 242 FAILs.

Native i686-pc-linux-gnu (Red Hat Linux 6.0):

  === gdb Summary ===
  # of ERRORs                     16
  # of WARNINGs                   0
  # of expected passes            7528
  # of unexpected failures        133
  # of unexpected successes       26
  # of expected failures          195
  # of unresolved testcases       15
  # of untested testcases         1
  # of unsupported tests          2
  === libiberty regress-demangle ===
  All 645 tests passed

Native i686-pc-linux-gnu (Red Hat Linux 6.1):

  === gdb Summary ===
  # of ERRORs                     16
  # of WARNINGs                   0
  # of expected passes            7530
  # of unexpected failures        131
  # of unexpected successes       26
  # of expected failures          195
  # of unresolved testcases       15
  # of untested testcases         1
  # of unsupported tests          2
  === libiberty regress-demangle ===
  All 645 tests passed

Native i686-pc-linux-gnu (Red Hat Linux 6.2):

  === gdb Summary ===
  # of ERRORs                     16
  # of WARNINGs                   0
  # of expected passes            7590
  # of unexpected failures        144
  # of unexpected successes       27
  # of expected failures          194
  # of unresolved testcases       15
  # of untested testcases         1
  === libiberty regress-demangle ===
  All 645 tests passed

Native i686-pc-linux-gnu (Red Hat Linux 7):

  === gdb Summary ===
  # of ERRORs                     16
  # of WARNINGs                   0
  # of expected passes            7597
  # of unexpected failures        137
  # of unexpected successes       26
  # of expected failures          195
  # of unresolved testcases       15
  # of untested testcases         1
  === libiberty regress-demangle ===
  All 645 tests passed

Native sparc-sun-solaris2.5.1:

  === gdb Summary ===
  # of ERRORs                     1
  # of WARNINGs                   0
  # of expected passes            7610
  # of unexpected failures        171
  # of unexpected successes       27
  # of expected failures          194
  # of unresolved testcases       33
  # of untested testcases         1
  === libiberty regress-demangle ===
  All 645 tests passed

Native sparc-sun-solaris2.6:

  === gdb Summary ===
  # of ERRORs                     0
  # of WARNINGs                   0
  # of expected passes            7612
  # of unexpected failures        171
  # of unexpected successes       27
  # of expected failures          194
  # of unresolved testcases       32
  # of untested testcases         1
  === libiberty regress-demangle ===
  All 645 tests passed

Native sparc-sun-solaris2.7:

  === gdb Summary ===
  # of ERRORs                     1
  # of WARNINGs                   0
  # of expected passes            7588
  # of unexpected failures        193
  # of unexpected successes       26
  # of expected failures          195
  # of unresolved testcases       33
  # of untested testcases         1
  === libiberty regress-demangle ===
  All 645 tests passed

Native sparc-sun-solaris2.8:

  === gdb Summary ===
  # of ERRORs                     1
  # of WARNINGs                   0
  # of expected passes            7577
  # of unexpected failures        204
  # of unexpected successes       26
  # of expected failures          195
  # of unresolved testcases       33
  # of untested testcases         1
  === libiberty regress-demangle ===
  All 645 tests passed

I ran the tests with FSF gcc cvs gcc-3_0-branch dated 2001-06-29 and FSF
gdb cvs dated 2001-06-23.  gcc 3.0 has been released, but I am still using
the branch in anticipation that it will become gcc 3.0.1.

Starting this week, I am running the libiberty test suite.  This test
suite includes a test script for the C++ demangler.  Right now the
demangler test script has cases for v2, but not for v3.

All hosts were available this week.

I counted the ERROR and WARNING lines by hand.

All results are in Terf, http://sources.redhat.com/cgi-bin/gdb.cgi .
Note that Terf does not report ERRORs or WARNINGs.  Also, Terf has
problems with duplicate test names.

Here are the merged ERRORs categorized by test script:

   17 TOTAL
   == =====
    1 gdb.base/shlib-call.exp
   16 gdb.mi/mi-*.exp

The changes from 2001-06-23 are:

  2001-06-23 total        1 ERRORs
  gdb.mi/mi-*.exp       +16 ERRORs  ERROR: Breakpoints not deleted
  2001-06-29 total       17 ERRORs

gdb.base/shlib-call.exp:

  This script produces 1 ERROR on native sparc-sun-solaris-{2.5.1,2.7,2.8):

    run
    The program being debugged has been started already.
    Start it from the beginning? (y or n) ERROR: Got interactive prompt.
    UNRESOLVED: gdb.base/shlib-call.exp: re-run to bp in shared library (PR's 16495, 18213)

  I have not analyzed this ERROR.

gdb.mi/mi-*.exp:

  These scripts produce 16 instancees of this ERROR on native
  i686-pc-linux-gnu (red hat linux 6.0, 6.1, 6.2, 7):

    ERROR: Breakpoints not deleted

  I have analyzed this and submitted PR gdb/73.

Here are the merged FAILs categorized by test script:

    242 TOTAL
    === =====
      3 gdb.base/annota1.exp
      1 gdb.base/break.exp
      1 gdb.base/call-rt-st.exp
     11 gdb.base/callfwmall.exp
      4 gdb.base/completion.exp
      1 gdb.base/corefile.exp
      1 gdb.base/default.exp
      4 gdb.base/ena-dis-br.exp
      2 gdb.base/ending-run.exp
      1 gdb.base/page.exp
      2 gdb.base/return2.exp
      4 gdb.base/selftest.exp
      8 gdb.base/shlib-call.exp
      1 gdb.base/sigall.exp
      7 gdb.base/signals.exp
      3 gdb.base/so-impl-ld.exp
      6 gdb.base/step-line.exp
      2 gdb.base/structs2.exp
      2 gdb.base/watchpoint.exp
      3 gdb.c++/annota2.exp
     18 gdb.c++/classes.exp
      8 gdb.c++/cplusfuncs.exp
      1 gdb.c++/demangle.exp
      4 gdb.c++/derivation.exp
      6 gdb.c++/inherit.exp
      2 gdb.c++/local.exp
      5 gdb.c++/method.exp
      2 gdb.c++/namespace.exp
      1 gdb.c++/overload.exp
     12 gdb.c++/ovldbreak.exp
      6 gdb.c++/templates.exp
      1 gdb.c++/userdef.exp
     31 gdb.c++/virtfunc.exp
      1 gdb.mi/mi-basics.exp
      1 gdb.mi/mi-break.exp
      1 gdb.mi/mi-console.exp
      2 gdb.mi/mi-hack-cli.exp
      3 gdb.mi/mi-regs.exp
      2 gdb.mi/mi-simplerun.exp
      9 gdb.mi/mi-stack.exp
      1 gdb.mi/mi-stepi.exp
      3 gdb.mi/mi-var-block.exp
      3 gdb.mi/mi-var-child.exp
      4 gdb.mi/mi-var-cmd.exp
      8 gdb.mi/mi-var-display.exp
      1 gdb.mi/mi0-break.exp
      1 gdb.mi/mi0-console.exp
      1 gdb.mi/mi0-hack-cli.exp
      2 gdb.mi/mi0-regs.exp
      2 gdb.mi/mi0-simplerun.exp
      9 gdb.mi/mi0-stack.exp
      1 gdb.mi/mi0-stepi.exp
      3 gdb.mi/mi0-var-block.exp
      4 gdb.mi/mi0-var-child.exp
      4 gdb.mi/mi0-var-cmd.exp
      8 gdb.mi/mi0-var-display.exp
      1 gdb.stabs/weird.exp
      2 gdb.threads/pthreads.exp
      1 gdb.trace/packetlen.exp

The changes from 2001-06-23 are:

  2001-06-23 total             175 FAILs
  gdb.base/annota1.exp          +1 FAILs  "warning: procfs: resume can't ..."
  gdb.base/break.exp            +1 FAILs  "warning: procfs: resume can't ..."
  gdb.base/call-rt-st.exp       +1 FAILs  "warning: procfs: resume can't ..."
  gdb.base/ena-dis-br.exp       +4 FAILs  "warning: procfs: resume can't ..."
  gdb.base/page.exp             -1 FAILs  dejagnu parser glitch
  gdb.base/sigall.exp           +1 FAILs  "warning: procfs: resume can't ..."
  gdb.base/signals.exp          +2 FAILs  "warning: procfs: resume can't ..."
  gdb.base/watchpoint.exp       +2 FAILs  "warning: procfs: resume can't ..."
  gdb.c++/annota2.exp           +1 FAILs  "warning: procfs: resume can't ..."
  gdb.c++/method.exp            +1 FAILs  "warning: procfs: resume can't ..."
  gdb.c++/ovldbreak.exp        +12 FAILs  "warning: procfs: resume can't ..."
  gdb.mi/mi-basics.exp          +1 FAILs  not analyzed
  gdb.mi/mi-hack-cli.exp        +1 FAILs  not analyzed
  gdb.mi/mi-regs.exp            +1 FAILs  not analyzed
  gdb.mi/mi-simplerun.exp       +1 FAILs  not analyzed
  gdb.mi/mi-stack.exp           +3 FAILs  not analyzed
  gdb.mi/mi-stepi.exp           +1 FAILs  not analyzed
  gdb.mi/mi-var-block.exp       +3 FAILs  not analyzed
  gdb.mi/mi-var-child.exp       +3 FAILs  not analyzed
  gdb.mi/mi-var-cmd.exp         +3 FAILs  not analyzed
  gdb.mi/mi-var-display.exp     +5 FAILs  not analyzed
  gdb.mi/mi0-simplerun.exp      +1 FAILs  not analyzed
  gdb.mi/mi0-stack.exp          +3 FAILs  not analyzed
  gdb.mi/mi0-stepi.exp          +1 FAILs  not analyzed
  gdb.mi/mi0-var-block.exp      +3 FAILs  not analyzed
  gdb.mi/mi0-var-child.exp      +4 FAILs  not analyzed
  gdb.mi/mi0-var-cmd.exp        +3 FAILs  not analyzed
  gdb.mi/mi0-var-display.exp    +5 FAILs  not analyzed
  2001-06-29 total             242 FAILs

FAIL: gdb.base/annota1.exp: run until main breakpoint
FAIL: gdb.base/break.exp: hit silent break 79
FAIL: gdb.base/call-rt-st.exp: finish out from loop_count
FAIL: gdb.base/ena-dis-br.exp: continue until exit at no stop at auto-disabled break marker2
FAIL: gdb.base/ena-dis-br.exp: continue until exit at no stop at ignored break marker1
FAIL: gdb.base/ena-dis-br.exp: continue until exit at no stop at ignored & auto-deleted break marker1
FAIL: gdb.base/ena-dis-br.exp: continue until exit at no stop at ignored & disabled break marker1
FAIL: gdb.base/sigall.exp: continue until exit at continue to sigall exit
FAIL: gdb.base/signals.exp: p func1 () #1 in signals.exp
FAIL: gdb.base/signals.exp: continue in signals.exp
FAIL: gdb.base/watchpoint.exp: continue until exit at continue to exit in test_simple_watchpoint
FAIL: gdb.base/watchpoint.exp: continue until exit at continue to exit in test_disabling_watchpoints
FAIL: gdb.c++/annota2.exp: continue to exit
FAIL: gdb.c++/method.exp: finish program
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : char
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : signed char
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : unsigned char
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : short
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : unsigned short
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : int
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : (unsigned|unsigned int)
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : long
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : unsigned long
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : float
FAIL: gdb.c++/ovldbreak.exp: continue to bp overloaded : double
FAIL: gdb.c++/ovldbreak.exp: continue until exit at finish program

  These are regression FAILs in sparc-sun-solaris-{2.5.1,2.6,2.7,2.8}.

  gdb prints many new instances of this warning message,
  which intereferes with the test script:

    warning: procfs: resume can't find thread 1 -- resuming all.

  I filed PR gdb/74 for these FAILs.

PASS: gdb.base/page.exp: info set

  The test script issues an "info set" command and looks at the result.
  It actually does this twice, with identical test names.

  This is parsing or buffering issue in TCL/Expect/Dejagnu.  The "info
  set" command reports the current prompt, among many other things.
  On sparc-sun-solaris2.8, Dejagnu would take that information in
  the middle of the block and match it against $gdb_prompt.  Now in
  2001-06-30, this pair of tests returns PASS/FAIL.  Thus, one of the
  twin tests changed from FAIL to PASS; the other twin stayed from FAIL
  to FAIL.

  I can't point to any identifiable change on my host or in gdb to
  account for this.

gdb.mi/mi-basics.exp
gdb.mi/mi-hack-cli.exp
gdb.mi/mi-regs.exp
gdb.mi/mi-simplerun.exp
gdb.mi/mi-stack.exp
gdb.mi/mi-stepi.exp
gdb.mi/mi-var-block.exp
gdb.mi/mi-var-child.exp
gdb.mi/mi-var-cmd.exp
gdb.mi/mi-var-display.exp
gdb.mi/mi0-simplerun.exp
gdb.mi/mi0-stack.exp
gdb.mi/mi0-stepi.exp
gdb.mi/mi0-var-block.exp
gdb.mi/mi0-var-child.exp
gdb.mi/mi0-var-cmd.exp
gdb.mi/mi0-var-display.exp

  GDB MI is still new.  I have not analyzed these FAILs.


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