public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/17756] gdb find command returns bogus results and can't find the matched value. Date: Thu, 23 Jul 2020 19:07:08 +0000 [thread overview] Message-ID: <bug-17756-4717-cN1rDyQn1a@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17756-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17756 --- Comment #6 from Tom Tromey <tromey at sourceware dot org> --- (In reply to Pedro Alves from comment #3) Off by one makes my head hurt. > Mapped address spaces: > > 0x7ffffffdd000 0x7ffffffff000 0x22000 0x0 [stack] I think this range is exclusive on the high end? That is 0x7ffffffff000 is not included. > (gdb) find /b 0x7ffffffdd000, 0x7ffffffff000, 0xa5 However "find" is inclusive on the high end. Probably a bad choice (IMO) but on the other hand, maybe more confusing to change it at this point. So, I don't think there's a bug here. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-07-23 19:07 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-25 9:20 [Bug gdb/17756] New: " liuyefenglin at gmail dot com 2014-12-25 9:32 ` [Bug gdb/17756] " liuyefenglin at gmail dot com 2014-12-27 8:44 ` dje at google dot com 2015-08-07 17:35 ` matt.street at gmail dot com 2015-08-07 17:57 ` palves at redhat dot com 2020-07-23 17:33 ` tromey at sourceware dot org 2020-07-23 19:00 ` tromey at sourceware dot org 2020-07-23 19:07 ` tromey at sourceware dot org [this message] 2020-07-23 19:35 ` tromey at sourceware dot org 2020-10-07 18:13 ` cvs-commit at gcc dot gnu.org 2020-10-07 18:23 ` 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-17756-4717-cN1rDyQn1a@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).