From: Colin MacDonald <colin_mac2002@yahoo.co.uk>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: Unable to step over functions in arm-elf binary
Date: Thu, 22 Feb 2007 16:46:00 -0000 [thread overview]
Message-ID: <20070222125604.64631.qmail@web26704.mail.ukl.yahoo.com> (raw)
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.
Colin MacDonald
----- Original Message ----
From: Daniel Jacobowitz <drow@false.org>
To: Colin MacDonald <colin_mac2002@yahoo.co.uk>
Cc: gdb@sourceware.org
Sent: Thursday, 22 February, 2007 12:27:23 PM
Subject: Re: Unable to step over functions in arm-elf binary
On Thu, Feb 22, 2007 at 11:48:53AM +0000, Colin MacDonald wrote:
> We have .elf targets for Arm processors and we can debug these via a remote connection (using the remote serial protocol) with Insight / GDB. Everything works fine except for one thing: I can't step over a function. If I try to step over a function I invariably step into it instead. Using the 'n' command from GDB command line generates a sequence remote serial commands like this:
You didn't say what version of GDB you're using. Try a newer one? It
sounds like yours fails to backtrace after stepping in to a function.
--
Daniel Jacobowitz
CodeSourcery
___________________________________________________________
All New Yahoo! Mail – Tired of unwanted email come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html
next reply other threads:[~2007-02-22 12:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 16:46 Colin MacDonald [this message]
2007-02-22 16:50 ` Daniel Jacobowitz
-- 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=20070222125604.64631.qmail@web26704.mail.ukl.yahoo.com \
--to=colin_mac2002@yahoo.co.uk \
--cc=drow@false.org \
--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