Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: michael <michael@evidence.eu.com>
To: gdb@sourceware.org
Subject: gdbserver on sh4
Date: Fri, 13 Mar 2009 11:23:00 -0000	[thread overview]
Message-ID: <49BA416E.6090901@evidence.eu.com> (raw)

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






             reply	other threads:[~2009-03-13 11:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 11:23 michael [this message]
2009-03-14  7:58 ` michael
2009-03-31  5:46   ` binom
2009-03-31  8:26     ` Michael Trimarchi
2009-03-31  8:56       ` Paul Mundt
2009-03-31  9:05         ` Michael Trimarchi
2009-03-31  9:07           ` Paul Mundt
2009-03-31  9:11             ` Michael Trimarchi
2009-06-19 15:56               ` damien.courousse.logica
2009-06-19 16:05                 ` michael
2009-06-19 16:14                   ` damien.courousse.logica
     [not found]                   ` <F81DF98CADE6064F81A746D7C832359367160A@fr-ex009.groupinfra.com>
2009-06-19 16:20                     ` michael

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49BA416E.6090901@evidence.eu.com \
    --to=michael@evidence.eu.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox