From: Daniel Jacobowitz <drow@false.org>
To: Colin MacDonald <colin_mac2002@yahoo.co.uk>
Cc: gdb@sourceware.org
Subject: Re: Unable to step over functions in arm-elf binary
Date: Thu, 22 Feb 2007 16:50:00 -0000 [thread overview]
Message-ID: <20070222131259.GA27665@caradoc.them.org> (raw)
In-Reply-To: <20070222125604.64631.qmail@web26704.mail.ukl.yahoo.com>
On Thu, Feb 22, 2007 at 12:56:04PM +0000, Colin MacDonald wrote:
> I'm using GDB / Insight 6.5. First attempts with 6.6 appear to show the same behaviour.
>
> I updated my remote serial server to support $vCont packets as well as the basic $c and $s packets but no joy.
I recommend you single step (using stepi) to the first instruction of
a function you can't "next" over, and try "backtrace". If it's wrong,
that's your problem. Keep stepi'ing a bit until you're into the
function body.
Another thing that may be helpful is "set debug infrun 1".
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-22 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 16:46 Colin MacDonald
2007-02-22 16:50 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-22 19:26 Colin MacDonald
2007-02-23 0:10 ` Daniel Jacobowitz
2007-02-22 12:56 Colin MacDonald
2007-02-22 13:13 ` Daniel Jacobowitz
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=20070222131259.GA27665@caradoc.them.org \
--to=drow@false.org \
--cc=colin_mac2002@yahoo.co.uk \
--cc=gdb@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