summaryrefslogtreecommitdiff
path: root/opcodes
diff options
context:
space:
mode:
authorBruno Larsen <blarsen@redhat.com>2023-02-21 17:10:31 +0100
committerBruno Larsen <blarsen@redhat.com>2023-02-27 10:52:23 +0100
commita3da2e7e550c4fe79128b5e532dbb90df4d4f418 (patch)
tree0d17df26d12917fe5ee6c4242b258c657615822d /opcodes
parent4e08903f679f22be6d7ea6e33f21a9fc43210567 (diff)
downloadbinutils-gdb-a3da2e7e550c4fe79128b5e532dbb90df4d4f418.tar.gz
gdb/testsuite: Improve testing of GDB's completion functions
When looking at some failures of gdb.linespec/cp-completion-aliases.exp, I noticed that when a completion test will fail, it always fails with a timeout. This is because most completion tests use gdb_test_multiple and only add a check for the correct output. This commit adds new options for both, tab and command completion. For command completion, the new option will check if the prompt was printed, and fail in this case. This is enough to know that the test has failed because the check comes after the PASS path. For tab completion, we have to check if GDB outputted more than just the input line, because sometimes GDB would have printed a partial line before finishing with the correct completion. Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'opcodes')
0 files changed, 0 insertions, 0 deletions