From: Daniel Jacobowitz <drow@false.org>
To: Paul Blacquiere <blacq@slingshot.co.nz>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Howto single step from beginning
Date: Thu, 02 Feb 2006 13:52:00 -0000 [thread overview]
Message-ID: <20060202135230.GA32388@nevyn.them.org> (raw)
In-Reply-To: <20060202182905.ac0ckos04gk00wso@webmail.slingshot.co.nz>
On Thu, Feb 02, 2006 at 06:29:05PM +1300, Paul Blacquiere wrote:
> >
> >Remind me again what version of GDB you're using? And it is configured
> >for arm-linux, right? Or maybe you're debugging a uClibc static binary
> >that doesn't have the correct ABI markings?
>
> GDB Ver 6.3 build under buildroot using uCLibc
That's why. Some versions of uClibc do not include a Linux ABI marker;
see what "objdump -s -j .note.ABI-tag" on the static binary you are
debugging shows. I think this has been fixed.
> >That's an arm-elf breakpoint. It doesn't work on arm-linux systems.
> >
> >Does "show osabi" reveal anything?
> >
> ----
> (gdb) show osabi
> The current OS ABI is "auto" (currently "ARM APCS").
> The default OS ABI is "GNU/Linux".
> (gdb)
> ----
Also GDB 6.3 would erroneously override the default ABI, as you see
here. Try 6.4 instead.
> I am assuming that the ABI markings are involved in the definition of
> the break
> point instruction, as I can not find a corresponding match to the gdb trace
> instruction in the gdb source.
Look for ARM_BE_BREAKPOINT in arm-tdep.c.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-02 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 1:08 Paul Blacquiere
2006-02-02 1:26 ` Daniel Jacobowitz
2006-02-02 2:52 ` Paul Blacquiere
2006-02-02 2:57 ` Daniel Jacobowitz
2006-02-02 3:20 ` Paul Blacquiere
2006-02-02 4:45 ` Paul Blacquiere
2006-02-02 5:07 ` Daniel Jacobowitz
2006-02-02 5:29 ` Paul Blacquiere
2006-02-02 13:52 ` Daniel Jacobowitz [this message]
2006-02-03 0:09 ` Paul Blacquiere
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=20060202135230.GA32388@nevyn.them.org \
--to=drow@false.org \
--cc=blacq@slingshot.co.nz \
--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