mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2024-12-21 04:42:53 +08:00
de28a3b72e
When running gdb.linespec/explicit.exp with check-read1, we get:
...
(gdb) PASS: gdb.linespec/explicit.exp: set max-completions unlimited
break
-function
...
top
(gdb) PASS: gdb.linespec/explicit.exp: complete with no arguments
break
-function
...
top
(gdb) FAIL: gdb.linespec/explicit.exp: complete with no arguments (clearing input line)
...
The problem is that the send_gdb "\t\t" triggers completion twice:
...
set tst "complete with no arguments"
send_gdb "break \t"
gdb_test_multiple "" $tst {
"break \\\x07" {
send_gdb "\t\t"
gdb_test_multiple "" $tst {
...
}
clear_input_line $tst
...
but the following gdb_test_multiple only parses it once, so the second
completion is left for clear_input_line, which fails.
Fix this by triggering completion only once.
Tested on x86_64-linux.
gdb/testsuite/ChangeLog:
2019-07-29 Tom de Vries <tdevries@suse.de>
* gdb.linespec/explicit.exp: Fix completion trigger for "complete with
no arguments".
|
||
|---|---|---|
| .. | ||
| base | ||
| 3explicit.c | ||
| body.h | ||
| break-ask.exp | ||
| break-asm-file0.s | ||
| break-asm-file1.s | ||
| break-asm-file.c | ||
| break-asm-file.exp | ||
| cpcompletion.exp | ||
| cpexplicit.cc | ||
| cpexplicit.exp | ||
| cpls2.cc | ||
| cpls-abi-tag.cc | ||
| cpls-abi-tag.exp | ||
| cpls-hyphen.cc | ||
| cpls-ops.cc | ||
| cpls-ops.exp | ||
| cpls.cc | ||
| explicit2.c | ||
| explicit.c | ||
| explicit.exp | ||
| keywords.c | ||
| keywords.exp | ||
| linespec.exp | ||
| ls-dollar.cc | ||
| ls-dollar.exp | ||
| ls-errs.c | ||
| ls-errs.exp | ||
| lspec.cc | ||
| lspec.h | ||
| macro-relative.c | ||
| macro-relative.exp | ||
| skip-two.exp | ||
| thread.c | ||
| thread.exp | ||