aboutsummaryrefslogtreecommitdiff
path: root/gdb/findcmd.c
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2019-02-14 07:58:58 -0700
committerTom Tromey <tromey@adacore.com>2019-02-20 08:21:46 -0700
commitc763b8943348582e651dda24f88bb9f8db24672b (patch)
tree0fb2aa7d2b81454433ab87643a067f454e5c3879 /gdb/findcmd.c
parent0ef8a082c32f34827479f2df8fbd431e08acd2d8 (diff)
downloadgdb-c763b8943348582e651dda24f88bb9f8db24672b.zip
gdb-c763b8943348582e651dda24f88bb9f8db24672b.tar.gz
gdb-c763b8943348582e651dda24f88bb9f8db24672b.tar.bz2
Use upper case for metasyntactic variables in "help find"
While answering a user's question on irc, I realized that the metasyntactic variables in "help find" are not in upper case. As you know this is one of my pet quests, so here is a patch to fix this. Tested on x86-64 Fedora 29. gdb/ChangeLog 2019-02-20 Tom Tromey <tromey@adacore.com> * findcmd.c (_initialize_mem_search): Use upper case for metasyntactic variables.
Diffstat (limited to 'gdb/findcmd.c')
-rw-r--r--gdb/findcmd.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/gdb/findcmd.c b/gdb/findcmd.c
index cd46100..52f8f80 100644
--- a/gdb/findcmd.c
+++ b/gdb/findcmd.c
@@ -286,9 +286,9 @@ _initialize_mem_search (void)
add_cmd ("find", class_vars, find_command, _("\
Search memory for a sequence of bytes.\n\
Usage:\nfind \
-[/size-char] [/max-count] start-address, end-address, expr1 [, expr2 ...]\n\
-find [/size-char] [/max-count] start-address, +length, expr1 [, expr2 ...]\n\
-size-char is one of b,h,w,g for 8,16,32,64 bit values respectively,\n\
+[/SIZE-CHAR] [/MAX-COUNT] START-ADDRESS, END-ADDRESS, EXPR1 [, EXPR2 ...]\n\
+find [/SIZE-CHAR] [/MAX-COUNT] START-ADDRESS, +LENGTH, EXPR1 [, EXPR2 ...]\n\
+SIZE-CHAR is one of b,h,w,g for 8,16,32,64 bit values respectively,\n\
and if not specified the size is taken from the type of the expression\n\
in the current language.\n\
Note that this means for example that in the case of C-like languages\n\