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:17:58 +0100 |
| commit | dee7b4c83a636471ee321fb4fe1c3be0a16a9ea7 (patch) | |
| tree | 7cca7c8f9d80b735aab6746745c9b13b68faba55 /libdecnumber/decSingleSymbols.h | |
| parent | dca0f6c0a4bafff9039d8bdb2a7efec9f70ce82f (diff) | |
| download | gdb-dee7b4c83a636471ee321fb4fe1c3be0a16a9ea7.zip gdb-dee7b4c83a636471ee321fb4fe1c3be0a16a9ea7.tar.gz gdb-dee7b4c83a636471ee321fb4fe1c3be0a16a9ea7.tar.bz2 | |
boolean/auto-boolean commands, make "o" ambiguous
We currently accept "o" with boolean/auto-boolean commands, taking it
to mean "on". But "o" is ambiguous, between "on" and "off". I can't
imagine why assuming the user wanted to type "on" is a good idea, it
might have been a typo.
This commit makes gdb error out. We now get:
(gdb) maint test-settings set boolean o
"on" or "off" expected.
(gdb) maint test-settings set auto-boolean o
"on", "off" or "auto" expected.
gdb/ChangeLog:
2019-06-13 Pedro Alves <palves@redhat.com>
* cli/cli-setshow.c (parse_auto_binary_operation)
(parse_cli_boolean_value): Don't allow "o".
gdb/testsuite/ChangeLog:
2019-06-13 Pedro Alves <palves@redhat.com>
* gdb.base/settings.exp (test-boolean, test-auto-boolean): Check
that "o" is ambiguous.
Diffstat (limited to 'libdecnumber/decSingleSymbols.h')
0 files changed, 0 insertions, 0 deletions