From: Tom Tromey Date: Thu, 14 Feb 2019 14:58:58 +0000 (-0700) Subject: Use upper case for metasyntactic variables in "help find" X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=c763b8943348582e651dda24f88bb9f8db24672b;p=binutils-gdb.git 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 * findcmd.c (_initialize_mem_search): Use upper case for metasyntactic variables. --- diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 721e636fdca..03419812a03 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2019-02-20 Tom Tromey + + * findcmd.c (_initialize_mem_search): Use upper case for + metasyntactic variables. + 2019-02-20 Alan Hayward * aarch64-tdep.c (aarch64_add_reggroups): New function. diff --git a/gdb/findcmd.c b/gdb/findcmd.c index cd461003d36..52f8f80aaae 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\