diff options
author | Pedro Alves <palves@redhat.com> | 2019-06-13 00:06:52 +0100 |
---|---|---|
committer | Pedro Alves <palves@redhat.com> | 2019-06-13 00:12:20 +0100 |
commit | dca0f6c0a4bafff9039d8bdb2a7efec9f70ce82f (patch) | |
tree | 6e37488519b942242e3b775854eb4ad6a7be3baa /gdb/NEWS | |
parent | ccf46844d3e5ad4af9f3a10cc0599c939138d566 (diff) | |
download | binutils-gdb-dca0f6c0a4bafff9039d8bdb2a7efec9f70ce82f.tar.gz |
New set/show testing framework (gdb.base/settings.exp)
This commit adds new representative commands for all types of settings
commands supported by gdb (enum var_types), and then uses them to
exercise settings parsing and completion.
(gdb) maint test-settings s[TAB]
set show
(gdb) maint test-settings set [TAB]
auto-boolean integer uinteger
boolean optional-filename zinteger
enum string zuinteger
filename string-noescape zuinteger-unlimited
(gdb) maint test-settings set enum [TAB]
xxx yyy zzz
etc.
This is basically unit testing, except that it goes fully via GDB. It
must be done this way in order to exercise TAB completion properly,
which must go via readline.
gdb/ChangeLog:
2019-06-13 Pedro Alves <palves@redhat.com>
* Makefile.in (COMMON_SFILES): Add maint-test-settings.c.
* NEWS: Mention maint test-settings KIND.
* maint-test-settings.c: New file.
gdb/doc/ChangeLog:
2019-06-13 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Maintenance Commands): Document "maint
test-settings" commands.
gdb/testsuite/ChangeLog:
2019-06-13 Pedro Alves <palves@redhat.com>
* gdb.base/settings.c: New file.
* gdb.base/settings.exp: New file.
Diffstat (limited to 'gdb/NEWS')
-rw-r--r-- | gdb/NEWS | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -84,6 +84,10 @@ set style highlight background COLOR set style highlight intensity VALUE Control the styling of highlightings. +maint test-settings KIND + A set of commands used by the testsuite for exercising the settings + infrastructure. + * Changed commands help |