This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: GDB-5 2000-03-03
- To: ac131313 at cygnus dot com
- Subject: Re: GDB-5 2000-03-03
- From: Mark Kettenis <kettenis at wins dot uva dot nl>
- Date: Fri, 3 Mar 2000 16:56:12 +0100
- CC: gdb-patches at sourceware dot cygnus dot com
- References: <38BFBD74.79263683@cygnus.com>
Date: Sat, 04 Mar 2000 00:26:12 +1100
From: Andrew Cagney <ac131313@cygnus.com>
MI tests
The MI testsuite falls over (lots of dejagnu errors) when the MI wasn't
build.
Even if I build MI, there are quite a few dejagnu errors:
ERROR: Undefined command "-file-clear".
UNRESOLVED: gdb.mi/mi-basics.exp: file-clear operation
FAIL: gdb.mi/mi-console.exp: Hello message (timeout)
...
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble from pc assembly only
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble main assembly only
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble range assembly only
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble callee2 assembly only
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble callee2 assembly mixed
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble range assembly mixed
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble callee2 assembly mixed
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble bogus arguments
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble wrong num of args (3)
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble wrong num of args (2)
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble wrong num of args (1)
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble from pc two lines - assembly only
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble main 1 line - assembly only
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble main zero lines - assembly only
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble lines bigger than range - assembly only
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble lines less than range - assembly only
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble from pc two lines - assembly mixed
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble main 1 line - assembly mixed
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble main zero lines - assembly mixed
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble lines bigger than range - assembly mixed
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble lines less than range - assembly mixed
...
FAIL: gdb.mi/mi-disassemble.exp: data-disassemble from pc assembly mixed
...
FAIL: gdb.mi/mi-simplerun.exp: exec-finish (timeout)
FAIL: gdb.mi/mi-simplerun.exp: continue to end (1)
...
FAIL: gdb.mi/mi-stack.exp: stack args listing 0
...
FAIL: gdb.mi/mi-stack.exp: stack args listing 1
...
FAIL: gdb.mi/mi-stack.exp: stack info-depth
...
FAIL: gdb.mi/mi-stack.exp: stack info-depth 99
...
FAIL: gdb.mi/mi-var-child.exp: update all vars psnp->next->long_ptr (and 1.long_ptr) changed
...
FAIL: gdb.mi/mi-var-cmd.exp: update all vars: changed FIXME
...
FAIL: gdb.mi/mi-watch.exp: list of watchpoints
...
FAIL: gdb.mi/mi-watch.exp: wp out of scope (2)
Here's the summary for i586-pc-linux-gnu:
=== gdb Summary ===
# of expected passes 6827
# of unexpected failures 45
# of expected failures 212
# of unresolved testcases 1
/mnt/hdb4/obj/src/gdb/testsuite/../../gdb/gdb version 20000204 -nx
The majority of all those unexpected failures is because of the MI
problems.
Mark