From: Jesper Skov <jskov@cygnus.co.uk>
To: dony <dony.he@huawei.com.cn>
Cc: Jesper Skov <jskov@cygnus.co.uk>,
linuxppc-embed <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: gdbserver
Date: Mon, 24 Jan 2000 09:20:49 +0100 (CET) [thread overview]
Message-ID: <14476.2913.868456.408641@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <388BB007.D0BF32C4@huawei.com.cn>
>>>>> "dony" == dony <dony.he@huawei.com.cn> writes:
dony> Jesper Skov wrote:
>> >>>>> "dony" == dony <dony.he@huawei.com.cn> writes:
>>
dony> Hello,
>>
dony> Now I want to use gdbserver to debug my test app. Running
dony> "gdbserver :6666 ./mytest" on the target (Powerpc 860) show a
dony> message: Process ./mytest created :pid=8 But I don't know how to
dony> run gdb on the host (X86). The README doesn't seem to explain
dony> clearly . It says first running "gdb mytest" on the host and
dony> 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> "powerpc-linux-gdb" is compiled with gcc or powerpc-linux-gcc?
gcc. You should look at one of the FAQ/HOWTO/READMEs/Home pages on the
sucject of embedded development. I think there was posted a small
howto on compiling the components a few days back. Check the archive.
One question: you are using an x86 host, right? If you use a PPC host,
you can just use the preinstalled GDB/GCC when building/debugging the
target binary.
dony>How do you build you powerpc-linux-gdb?
dony>I copy a gdb-4.17.tar.gz from LinuxPPC R4 CD.
dony>When I untar and decompress it, I type the following under gdb-4.17/gdb
dony>directory:
dony>
dony> ./configure --target=powerpc-linux
dony> make
dony>
dony> It fails to compile and say:
dony> make:*** No rule to make target `../bfd/bfd.h`, needed by `blockframe.o`.Stop.
dony>
dony>Yes, there is not bfd.h under gdb-4.17/bfd directory.
dony>Do you know why?
dony>Thank you very much.
I don't know why. It's an old debugger. I think we keep a more recent
version / CVS tree on sourceware.cygnus.com. It may work better. The
howto I mentioned before included links to the archives used, as far
as I remember.
Jesper
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-24 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-22 3:20 gdbserver dony
2000-01-22 10:27 ` gdbserver Jesper Skov
2000-01-24 1:51 ` gdbserver dony
2000-01-24 8:20 ` Jesper Skov [this message]
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 --
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=14476.2913.868456.408641@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 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 NNTP newsgroup(s).