This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/9310] nexti command does not work when debugging ARMassembly language
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 22 Nov 2012 18:50:20 +0000
- Subject: [Bug gdb/9310] nexti command does not work when debugging ARMassembly language
- Auto-submitted: auto-generated
- References: <bug-9310-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=9310
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |WAITING
--- Comment #4 from Pedro Alves <palves at redhat dot com> 2012-11-22 18:50:20 UTC ---
> "some android app without symbol"
I see. "nexti" works by internally:
#1 - single-stepping.
#2 - gdb's frame unwinder notices a new frame has been entered.
#3 - gdb figures out where the function will return to (unwinds the PC),
and sets a breakpoint at the return location.
#4 - let's the program run until that breakpoint is hit.
I'd guess that #3 is failing for you, due to missing unwind/debug info.
Try "stepi", and then "up" once. Does the PC point at where you'd expect
the bl/blx would return to?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.