diff options
author | Pedro Alves <palves@redhat.com> | 2019-06-13 00:06:53 +0100 |
---|---|---|
committer | Pedro Alves <palves@redhat.com> | 2019-06-13 00:21:29 +0100 |
commit | 272d4594343349a713f7d8967d90ae2413ecbc30 (patch) | |
tree | 25442ababced86788bc1bdd53f87be7d16daedde /gdb/stack.c | |
parent | e2a689da55d3feb7b79a141f69c4049112f59c91 (diff) | |
download | gdb-272d4594343349a713f7d8967d90ae2413ecbc30.zip gdb-272d4594343349a713f7d8967d90ae2413ecbc30.tar.gz gdb-272d4594343349a713f7d8967d90ae2413ecbc30.tar.bz2 |
Introduce complete_nested_command_line
This adds a completion helper routine that makes it possible for a
command that takes another command as argument, such as "frame apply
all COMMAND" as "thread apply all COMMAND", to complete on COMMAND,
and have the completion machinery recurse and complete COMMAND as if
you tried to complete "(gdb) COMMAND". I.e., we'll be able to
complete like this, for example:
(gdb) thread apply all -[TAB]
-c -ascending -q -s
(gdb) thread apply all -ascending frame apply all -[TAB]
-c -limit -past-entry -past-main -q -s
(gdb) thread apply all -ascending frame apply all -past-main print -[TAB]
-address -elements -pretty -symbol
-array -null-stop -repeats -union
-array-indexes -object -static-members -vtbl
(gdb) thread apply all -ascending frame apply all -past-main print glo[TAB]
global1 global2
Above, the completer function understands that "thread apply all" is a
command, and then parses "-ascending" successfully and understand that
the rest of the string is "thread apply all"'s operand. And then, the
process repeats for the "frame apply" command, and on and on.
gdb/ChangeLog:
2019-06-13 Pedro Alves <palves@redhat.com>
* completer.c (complete_nested_command_line): New.
(gdb_completion_word_break_characters_throw): Add assertion.
* completer.h (complete_nested_command_line): Declare.
Diffstat (limited to 'gdb/stack.c')
0 files changed, 0 insertions, 0 deletions