diff options
author | Andrew Burgess <andrew.burgess@embecosm.com> | 2021-01-08 10:27:58 +0000 |
---|---|---|
committer | Andrew Burgess <andrew.burgess@embecosm.com> | 2021-01-08 15:30:18 +0000 |
commit | d00f086803f2213bf4406278cd3e83d935e27096 (patch) | |
tree | 6a6a0ce352e24d42dc7e71aaab95d7a74ec3337a /gdb/rx-tdep.c | |
parent | ed20522215641bf3cd35929eef578a89ac07fa37 (diff) | |
download | gdb-d00f086803f2213bf4406278cd3e83d935e27096.zip gdb-d00f086803f2213bf4406278cd3e83d935e27096.tar.gz gdb-d00f086803f2213bf4406278cd3e83d935e27096.tar.bz2 |
gdb: add missing test for completion of invalid /FMT strings
This commit:
commit 3df8c6afdd6d38a7622ff5f4b1a64aff80334ab9
Date: Fri Nov 27 10:46:07 2020 +0000
gdb: fix potentially uninitialised variable
Was pushed with no test. Naughty!
The new test checks how GDB behaves when completing an invalid /FMT
string.
Currently GDB does no validation of the /FMT string during tab
completion, and just assumes that any /FMT string is valid and
complete when the user hits TAB. So:
(gdb) p/@@<TAB>
Will give:
(gdb) p/@@ <CURSOR IS HERE>
We already had a test in place for completion on a valid /FMT string,
but the above commit fixed a bug in the logic for completing invalid
/FMT strings. Now we have a test for this too.
gdb/testsuite/ChangeLog:
* gdb.base/completion.exp: Add a new test.
Diffstat (limited to 'gdb/rx-tdep.c')
0 files changed, 0 insertions, 0 deletions