From: Daniel Jacobowitz <drow@mvista.com>
To: "Stephen A. Witt" <sawitt@electra.rsc.raytheon.com>
Cc: gdb@sources.redhat.com
Subject: Re: Remote Debugging on IXDP425
Date: Wed, 03 Dec 2003 21:29:00 -0000 [thread overview]
Message-ID: <20031203212910.GB2649@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.56.0312021011110.16671@zeus.rsc.raytheon.com>
On Wed, Dec 03, 2003 at 11:17:18AM -0800, Stephen A. Witt wrote:
> Thanks very much for the response, very dumb mistake on my part. I had
> built a gdb with an arm-linux target, but I inadvertantly used the normal
> i386 gdb when I first tried this. Using the arm-linux gdb that I had
> built, with the information you provided, I found that the breakpoint
> instruction being sent was 0x01009fef. The correct bp inst for an IXP425
> (a big-endian CPU) is 0xef9f0001. So I modified the breakpoint instruction
> value in gdb to 0xef9f0001 and breakpoints work now.
This is a GDB bug fixed in more recent versions of GDB.
> There are some other problems, like when I do 'step' or 'next' I get a
> "ptrace: bogus breakpoint trap". Floating point variable display doesn't
> work. So I'm looking into these.
The former is a Linux kernel bug. I sent Russell an explanation of the
problem and got no response. Just turn off the message.
> I just hacked in the changed breakpoint instruction value but it seems the
> correct way to do it would be to tell gdb during configuration that the
> target is an xscale CPU, and conditionally compile in the correct value.
> At first I thought I hadn't built gdb properly, but it doesn't appear that
> gdb-6.0 really supports an IXP425. Is this true?
ARM/Linux in big endian mode is definitely still a black sheep. None
of the GNU tools really support it out of the box, only various
vendors' tools.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-12-03 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 1:15 Stephen A. Witt
2003-12-02 4:20 ` Ian Lance Taylor
2003-12-03 19:17 ` Stephen A. Witt
2003-12-03 21:29 ` Daniel Jacobowitz [this message]
2003-12-03 21:50 ` Stephen A. Witt
2003-12-03 22:24 ` Peter Reilley
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=20031203212910.GB2649@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=sawitt@electra.rsc.raytheon.com \
/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