This is the mail archive of the gdb-patches@sourceware.org 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]

Re: [PATCH v6 7/9] Explicit locations: add UI features for CLI


Keith Seitz <keiths@redhat.com> writes:

Hi Keith,

> +    set tst "complete unique function name"
> +    send_gdb "break -function mai\t"
> +    gdb_test_multiple "" $tst {
> +	"break -function mai\\\x07n" {
> +	    send_gdb "\n"
> +	    gdb_test "" ".*Breakpoint \[0-9\]+.*" $tst
> +	    gdb_test_no_output "delete \$bpnum" "delete $tst breakpoint"
> +	}
> +    }

I got some timeout FAILs on my ubuntu x86_64 machine.

(gdb) PASS: gdb.linespec/explicit.exp: complete -line with no value
break -function main FAIL: gdb.linespec/explicit.exp: complete unique function name (timeout)
break -function myfunc^H^H^H^H^Hain ^[[KFAIL: gdb.linespec/explicit.exp: complete non-unique function name (timeout)
break -function foo^H^H^Hmain FAIL: gdb.linespec/explicit.exp: complete non-existant function name (timeout)
break -source 3ex^G^H^H^H/home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.linespec/FAIL: gdb.linespec/explicit.exp: complete unique file name (timeout)
break -source exp^G^H^H^H/home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.linespec/FAIL: gdb.linespec/explicit.exp: complete non-unique file name (timeout)
break -source foo^G^H^H^H/home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.linespec/ERROR: Process no longer exists
UNRESOLVED: gdb.linespec/explicit.exp: complete non-existant file name

The fails are shown on Debian-s390x too,
https://www.sourceware.org/ml/gdb-testers/2015-q3/msg06879.html I
haven't look into them yet.

-- 
Yao (éå)


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