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: Fri, 23 Feb 2007 00:10:00 -0000 [thread overview]
Message-ID: <20070222195827.GA27076@caradoc.them.org> (raw)
In-Reply-To: <76964.36169.qm@web26713.mail.ukl.yahoo.com>
On Thu, Feb 22, 2007 at 04:55:55PM +0000, Colin MacDonald wrote:
> OK, so I have a breakpoint on a line that calls a function. When I hit the breakpoint the backtrace shows this:
>
> #0 CPlatform::RunTestSuite (this=0x207ffb4) at Common/Platform.cpp:113
> #1 0x01017db0 in main (argc=17253984, argv=0x0) at OtherFiles/Main.cpp:37
>
> This is fine so far. Line 113 of platform.cpp calls a function called vs_status. If I stepi until I first hit vs_status I get the following as the backtrace:
>
> #0 vs_status (pInBuf=0x0) at Common/PlatformIO.cpp:149
> #1 0x00000000 in ?? ()
>
> Doesn't look happy. If I execute another stepi then pInBuf is picked up. Another few stepi instructions then fills in the backtrace properly:
That's the bug, and nowhere else. You need to find out why it can't
unwind. Is your compiler emitting sufficiently bogus debug info that
GDB is confused? Or have some symbols been unexpectedly stripped from
the ELF file? Those are the usual culprits.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-22 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 19:26 Colin MacDonald
2007-02-23 0:10 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-22 16:46 Colin MacDonald
2007-02-22 16:50 ` 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=20070222195827.GA27076@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