Thanks Markus,

reading those now ... looks like you were getting identical to me ...
gdb assumes everything loads from 0x0

I've got round that by using the add-symbol-file

on target: (where ab/bb/sh is exec and atlas is my host)
gdb-server /ab/bb/sh atlas:12345

on host:
sh-linux-gdb
GNU gdb 6.7.1
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64 --target=sh-linux".
(gdb) target remote 192.168.1.100:12345

Remote debugging using 192.168.1.100:12345
0x0cec0050 in ?? ()

(gdb) add-symbol-file ./busybox_unstripped.gdb 0x0cec0050
add symbol table from file "./busybox_unstripped.gdb" at
        .text_addr = 0xcec0050
(y or n) y

Reading symbols from /opt/sh/7203/busybox-1.5.1/busybox_unstripped.gdb...done.
(gdb) b main

Breakpoint 1 at 0xcecca3c: file applets/busybox.c, line 62.
(gdb) c
Continuing.

Program received signal SIGINT, Interrupt.
0x0cec8c3e in pipe ()
(gdb) b input_tab
Breakpoint 2 at 0xced9e96: file libbb/lineedit.c, line 786.
(gdb) c
Continuing.

but my breakpoints don't work... I assume its just not been set up in
the ptrace on my arch yet.
Hope this helps you with your re-locations.

Cheers
--
Kieran


On 08/04/2008, Markus Franke <[EMAIL PROTECTED]> wrote:
> You are not the only one facing problems with gdb/gdbserver on uClinux. I 
> have same problems on a Coldfire microprocessor running uClinux.
>
>  See also the recent thread [Using gdb/gdbserver on m68knommu target] on 
> uclinux-dev.
>
>  Best regards,
>  Markus
>
>  Zitat von Kieran Bingham <[EMAIL PROTECTED]>:
>
>
>
> >  Hi Guys,
> >
> >  What support does GDB Server have on uClinux.
> >  Does it support the BinFlat format? or does it need patching?
> >
> >  I'm trying to build and run gdb_server .6.7.1 but it doesn't seem to know
> >  about the offsets of the binaries.
> >  It connects ok, and runs on the board, but executing makes it jump 
> > somewhere
> >  near 0x0 and of course ... die horribly with unaligned and unrecognized
> >  instructions.
> >
> >  Trying to get any information about the program doesn't work as it doesn't
> >  know where it is ;) - but reading and poking around memory remotely does
> >  seem to work ok.
> >  --
> >  Any help appreciated.
> >  Cheers
> >  Kieran
> >
> >
>
>
>
>
>
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev

Reply via email to