Fix typo in lookup_cmd_1 comment

gdb/ChangeLog:

	* cli/cli-decode.c (lookup_cmd_1): Fix typo in comment.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 90d25cf4a1f4ac161cb523b035a9c8c693b9610b..89bbb8fbaf71f94766be28f75463ba8c1bc4a053 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -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>
 
        * python/py-type.c (typy_legacy_template_argument): Update.

diff --git a/gdb/cli/cli-decode.c b/gdb/cli/cli-decode.c
index d3be93c4b83599c0b2aa9482ed03dde4690ee829..436a7ed4ca92ea177b0d0219e332afca91c19ab0 100644 (file)
--- a/gdb/cli/cli-decode.c
+++ b/gdb/cli/cli-decode.c
@@ -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",
    "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 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
    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