From: Jesper Skov <jskov@cygnus.co.uk>
To: dony <dony.he@huawei.com.cn>
Cc: linuxppc-embed <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: gdbserver
Date: 22 Jan 2000 11:27:06 +0100 [thread overview]
Message-ID: <otu2k6tn9h.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: dony's message of "Sat, 22 Jan 2000 11:20:43 +0800"
>>>>> "dony" == dony <dony.he@huawei.com.cn> writes:
dony> Hello,
dony> Now I want to use gdbserver to debug my test app.
dony> Running "gdbserver :6666 ./mytest" on the target (Powerpc 860)
dony> show a message: Process ./mytest created :pid=8 But I don't know
dony> how to run gdb on the host (X86). The README doesn't seem to
dony> explain clearly . It says first running "gdb mytest" on the host
dony> and then "target remote mytarget:6666". But I don't understand
dony> something about "gdb mytest" . At this time should I run a x86
dony> "gdb" or something like "powerpc-linux-gdb"? And the "mytest"?
mytest is the same executable you run on the target. gdb you run on
the host would be powerpc-linux-gdb (i.e., cross-debugger), thus:
target:> gdbserver :6666 ./mytest
host:> powerpc-linux-gdb mytest
[...]
(gdb) target remote mytarget:6666
dony> Is it compiled with x86 gcc or cross-compiled with
dony> "powerpc-linux-gcc"? Really I am very confused at this point:-((
mytest is compiled with powerpc-linux-gcc.
dony> Do you have any experience to share with me about how to build
dony> and run gdbserver? Or do you have any other debug tools which
dony> can be used in embedded-linux environment? The README for
dony> gdbserver is written by Stu Grossman and Fred Fish. Does
dony> someone know their email address? Thank you very much:-) dony
Yes I know their email addresses. But you don't want to hassle them
with this. Trust me :)
Jesper
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-22 10:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-22 3:20 gdbserver dony
2000-01-22 10:27 ` Jesper Skov [this message]
2000-01-24 1:51 ` gdbserver dony
2000-01-24 8:20 ` gdbserver Jesper Skov
2000-01-27 2:48 ` How to gdbserver dony
2000-01-27 10:46 ` Jesper Skov
2000-01-27 11:27 ` Looking for a better debug tool for embed-environment dony
2000-01-27 11:35 ` Jesper Skov
-- strict thread matches above, loose matches on Subject: below --
2007-06-26 15:20 [PATCH] generic clk API implementation for MIPS Franck Bui-Huu
2007-06-26 16:33 ` Atsushi Nemoto
2007-06-27 15:39 ` Christoph Hellwig
2007-06-28 2:22 ` Atsushi Nemoto
2007-06-28 8:37 ` Christoph Hellwig
2007-06-28 20:45 ` gdbserver Ratin Rahman (mratin)
2007-06-28 20:45 ` gdbserver Ratin Rahman (mratin)
2007-06-28 21:41 ` gdbserver David Daney
2007-06-28 22:19 ` gdbserver Ratin Rahman (mratin)
2007-06-28 22:19 ` gdbserver Ratin Rahman (mratin)
2002-03-12 19:22 gdbserver Lanny DeVaney
2002-03-12 20:45 ` gdbserver Johannes Stezenbach
2002-03-12 21:46 ` gdbserver Lanny DeVaney
2002-03-12 22:10 ` gdbserver Daniel Jacobowitz
2002-03-12 22:16 ` gdbserver Lanny DeVaney
2002-01-25 10:20 gdbserver Kristberg Karlsson
2000-01-21 12:38 gdbserver kd
1999-12-21 14:35 gdbserver kd
1999-12-21 16:05 ` gdbserver Jim Lewis
2000-01-21 7:25 ` gdbserver dony
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=otu2k6tn9h.fsf@thinktwice.zoftcorp.dk \
--to=jskov@cygnus.co.uk \
--cc=dony.he@huawei.com.cn \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.