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: "martin at minimum dot se" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 18 Sep 2014 07:15:42 +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 #13 from molsson <martin at minimum dot se> ---
I built master (with Weigand's patch) and I don't see the error message
anymore, so that part of the fix works. Thanks.
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. It might be
better to change the error message "Cannot find bounds of current function"
into "Cannot find bounds of current function, use stepi to continue instruction
by instruction".
Further, in my particular case I'm stepping inside
blink::RenderFullScreen::createPlaceholder() which is located in
libblink_web.cr.so and "info sharedlibrary" confirms that I do have debug
symbols loaded for this .so file. I guess this might be because of the "stack
frame detection heuristics" you mentioned?
What can I do to debug that part further?
--
You are receiving this mail because:
You are on the CC list for the bug.