public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/16930] find command end_address confusion, plus error message could be clearer Date: Wed, 07 Oct 2020 18:13:51 +0000 [thread overview] Message-ID: <bug-16930-4717-YYejAlYyas@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16930-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16930 --- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=3a135a918614676f3d5b6297714dfa235af3d59d commit 3a135a918614676f3d5b6297714dfa235af3d59d Author: Tom Tromey <tromey@adacore.com> Date: Wed Oct 7 12:07:55 2020 -0600 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. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-10-07 18:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-10 0:11 [Bug gdb/16930] New: " dje at google dot com 2020-07-23 18:33 ` [Bug gdb/16930] " tromey at sourceware dot org 2020-10-07 18:13 ` cvs-commit at gcc dot gnu.org [this message] 2020-10-07 18:21 ` tromey at sourceware dot org 2020-10-08 17:53 ` tromey at sourceware dot org
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=bug-16930-4717-YYejAlYyas@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).