Re: Remote Debugging on IXDP425

["Stephen A. Witt" <sawitt@electra.rsc.raytheon.com>]

On Mon, 1 Dec 2003, Ian Lance Taylor wrote:

> "Stephen A. Witt" <sawitt@electra.rsc.raytheon.com> writes:
>
> > I'm trying to get remote debugging using gdbserver on an IXDP425 target
> > board. I've built a cross gdb-6.0 that executes on an i386 with the target
> > set to arm-unknown-linux-gnu. The 'arm-unknown-linux-gnu-gdb' on my
> > development machine does connect and talk to the gdbserver running on the
> > target. I can start the program from gdb but breakpoints that I set don't
> > break the program. I turned on remote debugging (set debug remote 1) and
> > get the following:
> >
-- snip --
>
> That isn't the problem by itself.  If the remote target doesn't
> support `Z0', then gdb will try to set a breakpoint by writing
> directly to memory.  That's what you see it doing with the `m' request
> (read memory) followed by the 'X' request (binary download, which is
> also not supported), followed by the 'M' request (write memory).  The
> sequence above winds up writing the byte 0xcc to address 0x8ec0.
> Similarly, it writes the byte 0xcc to the address 0x87a0.
>
> So this is all fine.  At least, it would be fine if a one-byte 0xcc
> were an ARM breakpoint instruction.  Unfortunately, 0xcc is an i386
> breakpoint instruction.  So I would say that you are running a gdb
> configured for an i386 target and connecting to a gdbserver running on
> an ARM.  Don't do that.
>
> Ian
>

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.

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.

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?