This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/17756] gdb find command returns bogus results and can't find the matched value.
- From: "matt.street at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 07 Aug 2015 17:34:59 +0000
- Subject: [Bug gdb/17756] gdb find command returns bogus results and can't find the matched value.
- Auto-submitted: auto-generated
- References: <bug-17756-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17756
Matthew Street <matt.street at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matt.street at gmail dot com
--- Comment #2 from Matthew Street <matt.street at gmail dot com> ---
I just confirmed this with 7.9 from Ubuntu Precise 32. I also have confirmed it
with 7.4 installed on my mac with homebrew.
Short example, I can give my data if need be:
(gdb) info proc mapping
-snip-
0xbffdf000 0xc0000000 0x21000 0x0 [stack]
find.gdb:
break test
run
find /b 0xbffdf000, 0xc0000000, 0x00
$> gdb -x find.gdb ./a.out > find.log
warning: Unable to access target memory at 0xbfffc181, halting search
But 0xbfffc181 is accessible:
(gdb) x /b 0xbfffc181
0xbfffc181: 0
And a smaller search range works fine:
(gdb) find /b 0xbfffc181, 0xbfffc191, 0x00
0xbfffc181
0xbfffc182
0xbfffc183
0xbfffc184
0xbfffc185
0xbfffc186
0xbfffc187
0xbfffc188
0xbfffc189
0xbfffc18a
0xbfffc18b
0xbfffc18c
0xbfffc18d
0xbfffc18e
0xbfffc18f
0xbfffc190
0xbfffc191
17 patterns found.
--
You are receiving this mail because:
You are on the CC list for the bug.