diff options
| author | Tom Tromey <tromey@adacore.com> | 2023-08-31 11:59:06 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2023-09-01 06:48:07 -0600 |
| commit | b47a4f92de5c12ac8bdac57b0413e3e05d411832 (patch) | |
| tree | 4a1766b9091ee23049fc1ff98ecf05ecdaca6041 /gdb/mi/mi-cmd-var.c | |
| parent | dfab07b9ead66f08661325c03175e1df9210ccd7 (diff) | |
| download | gdb-b47a4f92de5c12ac8bdac57b0413e3e05d411832.zip gdb-b47a4f92de5c12ac8bdac57b0413e3e05d411832.tar.gz gdb-b47a4f92de5c12ac8bdac57b0413e3e05d411832.tar.bz2 | |
Fix "usage" errors for some MI varobj commands
I noticed that the "usage" error for -var-set-frozen mentioned the
wrong command name. Then I looked through the whole file and found a
couple other spots that didn't mention the command name at all. This
patch fixes all of these.
Reviewed-by: Kevin Buettner <kevinb@redhat.com>
Diffstat (limited to 'gdb/mi/mi-cmd-var.c')
| -rw-r--r-- | gdb/mi/mi-cmd-var.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/gdb/mi/mi-cmd-var.c b/gdb/mi/mi-cmd-var.c index 095790a..8b4dd6d 100644 --- a/gdb/mi/mi-cmd-var.c +++ b/gdb/mi/mi-cmd-var.c @@ -246,7 +246,7 @@ mi_cmd_var_set_visualizer (const char *command, const char *const *argv, struct varobj *var; if (argc != 2) - error (_("Usage: NAME VISUALIZER_FUNCTION.")); + error (_("-var-set-visualizer: Usage: NAME VISUALIZER_FUNCTION.")); var = varobj_get_handle (argv[0]); @@ -263,7 +263,7 @@ mi_cmd_var_set_frozen (const char *command, const char *const *argv, int argc) bool frozen; if (argc != 2) - error (_("-var-set-format: Usage: NAME FROZEN_FLAG.")); + error (_("-var-set-frozen: Usage: NAME FROZEN_FLAG.")); var = varobj_get_handle (argv[0]); @@ -442,7 +442,7 @@ mi_cmd_var_info_path_expression (const char *command, const char *const *argv, struct varobj *var; if (argc != 1) - error (_("Usage: NAME.")); + error (_("-var-info-path-expression: Usage: NAME.")); /* Get varobj handle, if a valid var obj name was specified. */ var = varobj_get_handle (argv[0]); |