[5/6] Document inclusive range in help for "find"

Message ID 20200723201216.3932150-6-tromey@adacore.com
State New
Headers show
  • Share memory searching code between gdb and gdbserver
Related show

Commit Message

Tom Tromey July 23, 2020, 8:12 p.m.
PR gdb/16930 points out that the "find" command uses an inclusive
range; but this is not documented in the "help".  This patch updates
the help text.

2020-07-23  Tom Tromey  <tromey@adacore.com>

	PR gdb/16930:
	* findcmd.c (_initialize_mem_search): Mention that the range is
 gdb/ChangeLog | 6 ++++++
 gdb/findcmd.c | 1 +
 2 files changed, 7 insertions(+)



diff --git a/gdb/findcmd.c b/gdb/findcmd.c
index c8631571f20..3e4a790b589 100644
--- a/gdb/findcmd.c
+++ b/gdb/findcmd.c
@@ -292,6 +292,7 @@  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\
+The two-address form specifies an inclusive range.\n\
 Note that this means for example that in the case of C-like languages\n\
 a search for an untyped 0x42 will search for \"(int) 0x42\"\n\
 which is typically four bytes, and a search for a string \"hello\" will\n\