gdbserver on sh4
michael
michael@evidence.eu.com
Sat Mar 14 07:58:00 GMT 2009
Hi,
michael wrote:
> Hi all,
>
> I crosscompile the gdb server for sh and I have trouble to debug a
> simple application,
> using it.
>
> I try with the gdb-6.8
>
> ./configure --target=sh4-linux
>
> gdbserver
> sh3-linux-gcc is a nptl toolchain
>
> CC=sh3-linux-gcc ./configure --host=sh4-linux
>
> server side
>
> ./gdbserver-6.8 192.168.10.156:1234
> ./foobar_sample Process ./foobar_sample created;
> pid = 817 Listening on port
> 1234 Remote
> debugging from host 192.168.8.242
>
> client side
> GNU gdb 6.8
> Copyright (C) 2008 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-unknown-linux-gnu
> --target=sh-linux"...
> (gdb) target remote 192.168.10.156:1234
> Remote debugging using 192.168.10.156:1234
> [New Thread 817]
> Got object file from memory but can't read symbols: File format not
> recognized.
> 0x00000000 in ?? ()
>
> This is how the toolchain is configured
> sh3-linux-gcc -v
> Using built-in specs.
> Target: sh3-linux
> Configured with: /home/kpit/fsfsrc/v0701/gcc-4.2-20061205/configure
> --host=i686-linux --target=sh3-linux
> --prefix=/usr/share/gnush4-nofpu_linux_v0701-1 --with-cpu=sh4-nofpu
> --with-sysroot=/usr/share/gnush4-nofpu_linux_v0701-1/sh3-linux/sys-root
> --with-local-prefix=/usr/share/gnush4-nofpu_linux_v0701-1/sh3-linux/sys-root
> --disable-nls --enable-threads --enable-symvers=gnu
> --disable-__cxa_atexit --enable-languages=c,c++ --enable-c99
> --enable-long-long --disable-multilib
>
> (gdb) b main
> Breakpoint 1 at 0x4003e6: file main.c, line 23.
> (gdb) c
> Continuing.
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0x7b9dedec in ?? ()
> (gdb)
>
> Can anybody help to find the problem?
>
> Kind regards
> Michael
>
>
>
>
>
>
I fix this problem, is not a gdb server or gdb problem.
Michael
More information about the Gdb
mailing list