public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/9310] nexti command does not work when debugging ARM assembly language
Date: Thu, 22 Nov 2012 18:50:00 -0000	[thread overview]
Message-ID: <bug-9310-4717-Zys2li8xrR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <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.


  parent reply	other threads:[~2012-11-22 18:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-9310-4717@http.sourceware.org/bugzilla/>
2012-10-26  8:40 ` zhudonghai at gmail dot com
2012-10-26 18:38 ` palves at redhat dot com
2012-10-27  9:10 ` zhudonghai at gmail dot com
2012-11-22 18:50 ` palves at redhat dot com [this message]
2013-10-30 17:32 ` will.newton at gmail dot com

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-9310-4717-Zys2li8xrR@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: link
Be 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).