I have seen something similar in our platform when the gdb on the host
computer was not compiled correctly.
For example it may be cross-compiled for mips n32 while the gdbserver is
compiled for o32, or similar incompatibilities.
I would double check that the toolchains used to compile the host gdb
and target gdbserver match.
Alex
>
> On Tue, 2005-07-19 at 14:52, Bryan Althouse wrote:
> > Is anyone doing remote debugging for mips?
> >
> > I start the gdbserver on mips with:
> > gdbserver 192.168.2.39:2222 ./hello_loop
> > This produces:
> > Process ./hello_loop created; pid = 158
> >
> > On my PC, I type:
> > ddd --debugger mips64-linux-gnu-gdb hello_loop
> > (at gdb prompt) target remote 192.168.2.55:2222
> >
> > This produces:
> > (on gdb prompt) Couldn't establish connection to remote target
> > Reply contains invalid hex digit 59
> > (on mips) Remote debugging from host 192.168.2.39
> > Readchar: Got EOF
> > Remote side has terminated connection. GDBserver will reopen the
> > connection.
> >
> > This problem is also described here:
> > http://mailman.uclinux.org/pipermail/uclinux-dev/2004-April/025421.html
> >
> > Any ideas? Thanks!
> >
> > Bryan
> >
|