summaryrefslogtreecommitdiff
path: root/gdb/findcmd.c
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2020-10-07 12:07:55 -0600
committerTom Tromey <tromey@adacore.com>2020-10-07 12:07:56 -0600
commit3a135a918614676f3d5b6297714dfa235af3d59d (patch)
treecc51327d11196aeb4298ad4f7424e0e8e44f700a /gdb/findcmd.c
parent60b746622b07063cdaae6207dd097576eca01128 (diff)
downloadbinutils-gdb-3a135a918614676f3d5b6297714dfa235af3d59d.tar.gz
Document inclusive range in help for "find"
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. gdb/ChangeLog 2020-10-07 Tom Tromey <tromey@adacore.com> PR gdb/16930: * findcmd.c (_initialize_mem_search): Mention that the range is inclusive.
Diffstat (limited to 'gdb/findcmd.c')
-rw-r--r--gdb/findcmd.c1
1 files changed, 1 insertions, 0 deletions
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\