Fix typo in lookup_cmd_1 comment

gdb/ChangeLog:

	* cli/cli-decode.c (lookup_cmd_1): Fix typo in comment.
This commit is contained in:
Simon Marchi 2017-01-11 11:15:26 -05:00
parent f2e2d2f54b
commit 4ad2da7317
2 changed files with 5 additions and 1 deletions

View File

@ -1,3 +1,7 @@
2017-01-11 Simon Marchi <simon.marchi@ericsson.com>
* cli/cli-decode.c (lookup_cmd_1): Fix typo in comment.
2017-01-10 Tom Tromey <tom@tromey.com> 2017-01-10 Tom Tromey <tom@tromey.com>
* python/py-type.c (typy_legacy_template_argument): Update. * python/py-type.c (typy_legacy_template_argument): Update.

View File

@ -1331,7 +1331,7 @@ valid_user_defined_cmd_name_p (const char *name)
if no prefix command was ever found. For example, in the case of "info a", if no prefix command was ever found. For example, in the case of "info a",
"info" matches without ambiguity, but "a" could be "args" or "address", so "info" matches without ambiguity, but "a" could be "args" or "address", so
*RESULT_LIST is set to the cmd_list_element for "info". So in this case *RESULT_LIST is set to the cmd_list_element for "info". So in this case
RESULT_LIST should not be interpeted as a pointer to the beginning of a RESULT_LIST should not be interpreted as a pointer to the beginning of a
list; it simply points to a specific command. In the case of an ambiguous list; it simply points to a specific command. In the case of an ambiguous
return *TEXT is advanced past the last non-ambiguous prefix (e.g. return *TEXT is advanced past the last non-ambiguous prefix (e.g.
"info t" can be "info types" or "info target"; upon return *TEXT has been "info t" can be "info types" or "info target"; upon return *TEXT has been