From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH v2 5/6] Document inclusive range in help for "find"
Date: Fri, 25 Sep 2020 13:49:12 -0600 [thread overview]
Message-ID: <20200925194913.1744541-6-tromey@adacore.com> (raw)
In-Reply-To: <20200925194913.1744541-1-tromey@adacore.com>
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-09-25 Tom Tromey <tromey@adacore.com>
PR gdb/16930:
* findcmd.c (_initialize_mem_search): Mention that the range is
inclusive.
---
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\
--
2.26.2
next prev parent reply other threads:[~2020-09-25 19:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 19:49 [PATCH v2 0/6] Share memory-searching code Tom Tromey
2020-09-25 19:49 ` [PATCH v2 1/6] Rename some tests in find.exp Tom Tromey
2020-09-25 19:49 ` [PATCH v2 2/6] Move simple_search_memory to gdbsupport/search.cc Tom Tromey
2020-09-25 19:49 ` [PATCH v2 3/6] Use simple_search_memory in gdbserver Tom Tromey
2020-09-25 19:49 ` [PATCH v2 4/6] Remove some dead code from handle_search_memory Tom Tromey
2020-09-28 15:13 ` Christian Biesinger
2020-09-28 19:46 ` Tom Tromey
2020-09-28 20:11 ` Christian Biesinger
2020-10-07 18:06 ` Tom Tromey
2020-09-25 19:49 ` Tom Tromey [this message]
2020-09-25 19:49 ` [PATCH v2 6/6] Add simple_search_memory unit tests Tom Tromey
2020-10-07 18:07 ` [PATCH v2 0/6] Share memory-searching code Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200925194913.1744541-6-tromey@adacore.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).