Using gdbserver for remote debugging -

["Robert S. Grimes" <rsg at alum dot mit dot edu>]

Hi,

I'm trying to get remote debugging working over the Ethernet.  I'm using
the Freescale MCF5329 ColdFire chip on the M5329EVB eval board,
uClinux-dist-20070130.tar.bz2 with some patches from a Freescale
AppNote(AN3408.pdf).  I selected the gdbserver option during "make
menuconfig" in userland.  I have built GDB 6.5 cross-debugger
m68k-elf-gdb.  All compiles and seems to get started okay, but failure
is just around the corner...

Here is what happens.  I start on the target -

Target:
 /> gdbserver :3000 /bin/hello
 Process /bin/hello created; pid = 26
 Listening on port 3000

So far, so good!  Then, on the host

Host:
 $ m68k-elf-gdb hello.gdb
 GNU gdb 6.5
 Copyright (C) 2006 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and
you are
 welcome to change it and/or distribute copies of it under certain
conditions.
 Type "show copying" to see the conditions.
 There is absolutely no warranty for GDB.  Type "show warranty" for
details.
 This GDB was configured as "--host=i686-pc-linux-gnu --target=m68k-elf"...
 (gdb) target remote 192.168.1.27:3000
 Remote debugging using 192.168.1.27:3000
 0x410076ce in ?? ()
 (gdb)

So it seems to connect okay, but I'm not sure about that line just
before the last prompt.  Anyway, back at the Target, I see an
encouraging message:

Target:
 Remote debugging from host 192.168.1.107

So I try to set a breakpoint back on the host:

Host:
 b main

The target dies!  Here is the output:

Target:
 Bad page state in process 'gdbserver'
 page:41b59000 flags:0x00000000 mapping:00000000 mapcount:1 count:0
 Trying to fix it up, but a reboot is needed
 Backtrace:
 Stack from 41047ec8:<0>
        <0> 00000000<0> 41047ed8<0> 40043298<0> 00000000<0> 41047efc<0>
40043ac0<0> 41b59000<0>  00000004<0>
        <0> 00000004<0> 0000001c<0> 00000000<0> 40048d10<0> 41b59000<0>
41047f0c<0> 40043b5a<0> 41b59000<0>
        <0> 00000000<0> 41047f28<0> 4004613c<0> 41b59000<0> 00000000<0>
40048d10<0> 41047f70<0> 41047f74<0>
        <0> 41047f34<0> 40046578<0> 41b59000<0> 41047f78<0> 4002f560<0>
41b59000<0> 0000001c<0> 41c23050<0>
        <0> 4107b692<0> 0000001c<0> 00000000<0> 0000001a<0> 00000000<0>
41c23050<0> 41078df4<0> 41078004<0>
        <0> 402021d0<0> 40202204<0> 41b59000<0> 4021a34e<0> 41047fa4<0>
4002117a<0> 41c23050<0> 0000001c<0>
 Call Trace:<0>
        <0> [<4002f984>]<0> [<4002f92a>]<0> [<40023c8a>]<0>

Any ideas?  Is this a version mismatch sort of problem?  Is gdb too
new?  If so, what version would work with the gdbserver from the uClinux
distro?

Or should I upgrade gdbserver, and if so, how?

I've been slugging through for a while on this, and seem to be a bit
stuck - any help would be greatly appreciated!!!

Thanks!
-Bob