List Info

Thread: Re: Unable to step over functions in arm-elf binary




Re: Unable to step over functions in arm-elf binary
country flaguser name
United States
2007-02-22 06:56:04
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 <drowfalse.org>
To: Colin MacDonald <colin_mac2002yahoo.co.uk>
Cc: gdbsourceware.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.doc
s.yahoo.com/nowyoucan.html

Re: Unable to step over functions in arm-elf binary
country flaguser name
United States
2007-02-22 07:12:59
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

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )