This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/17384] android arm gdb "Cannot access memory at address" when I "stepi" over "blx"
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 18 Sep 2014 07:28:02 +0000
- Subject: [Bug gdb/17384] android arm gdb "Cannot access memory at address" when I "stepi" over "blx"
- Auto-submitted: auto-generated
- References: <bug-17384-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17384
--- Comment #14 from Pedro Alves <palves at redhat dot com> ---
> Regarding gdb getting stuck in "Cannot find bounds of current function" errors
> I think there is some risk of confusion if gdb just switches to stepi silently
> because with "next" you expect it not to move into sub functions.
True. Seems like we may already have that with "set step-mode on" (*).
Maybe we could do "next" -> "nexti"; "step" -> "stepi".
(*) gosh, we should rename that setting to something that actually has meaning.
--
You are receiving this mail because:
You are on the CC list for the bug.