From: Daniel Jacobowitz <drow@mvista.com>
To: ???? ?? <lljforever@yahoo.com.cn>
Cc: gdb@sources.redhat.com
Subject: Re: I have some problem on gdbserver
Date: Fri, 15 Aug 2003 00:37:00 -0000 [thread overview]
Message-ID: <20030815003746.GA8819@nevyn.them.org> (raw)
In-Reply-To: <20030815001914.15371.qmail@web15311.mail.bjs.yahoo.com>
On Fri, Aug 15, 2003 at 08:19:14AM +0800, ???? ?? wrote:
> --- Daniel Jacobowitz <drow@mvista.com> ????????> On
> Thu, Aug 14, 2003 at 11:13:33PM +0800, ???? ??
> > wrote:
> > > Iwant to build cross-compile to my target, then I
> > > build
> > > gdbserver this way. for example:
> > > $ export CC=my-cross-compiler(arm-linu-gcc)
> > > $ path-to-gdbserver-sources/configure
> > > your-target-name(arm-linux)
> > > $ make
> > > But when I run gdbserver:
> > > $ arm-linux-gcc -g -o filename filename.c
> > > $ ./gdbserver host:1234 filename
> > > error:
> > > bash:./gdbserver:cannot execute binary file.
> > > Who can tell this is why?
> >
> > It looks like you are running gdbserver on the host.
> > It's supposed to
> > be run on the target.
> >
> >
> Thank you very much.It is true,I run the cross-gdb
> and gdbsever on the same host,but they cannot run on
> the same host in the remote way?Does gdb support
> communicating with target in TCP way on the same host?
>
> (I know cross gdb can debug programs in "target sim"
> way on the same host machine.)
> If I make gdbserver run on the target,must the
> target be the machine with arm cpu ,or can it be cross
> environment?
> regards!
Gdbserver the way you built it is an arm-linux binary. Run it on an
arm-linux machine.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-08-15 0:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 15:13 莉娟 刘
2003-08-14 15:16 ` Daniel Jacobowitz
2003-08-15 0:19 ` 莉娟 刘
2003-08-15 0:37 ` Daniel Jacobowitz [this message]
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=20030815003746.GA8819@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=lljforever@yahoo.com.cn \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).