From: Daris A Nevil <dnevil@snmc.com>
To: john zhan <johnzhan@btamail.net.cn>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: GDB for host development platform
Date: Fri, 10 Nov 2000 07:55:18 -0600 [thread overview]
Message-ID: <3A0BFE46.A7366165@snmc.com> (raw)
In-Reply-To: 006001bf448c$4aee3aa0$57c809c0@fel
John,
Sounds as though you did not connect to the target correctly. I have
written a procedure we use to connect to a PPC target over ethernet.
You can view this at:
http://qslinux.org/docs/cross/gdb/index.html
Hope this helps.
Regards,
Daris Nevil
john zhan wrote:
>
> I have now successfully build GDB-4.18 for linux/ppc.
> Both target and host are powerpc-linux.
> When I was trying to run a executable in my target
> hardware(8xx) with gdb(target for exec),
> e.g. hello,
> GDB said
> "
> Starting program: ./hello
> Don't know how to run. Try "help target".
> "
> Questions:
> 1. what's going on it?
> 2. Does(Did) anyone do the same thing?
> 3.The cross-debugger + target gdb server with a serial connection
> is the unique choices?
> 4. I wonder which is the best way to debug a linux/ppc application
> on the embedded platform.
> 5. What do you think a full host development environment
> (including native comilper,debugger etc) in the embedded
> system.
>
> thank for any response.
>
> regards.
> john zhan.
>
--
Daris A Nevil
Simple Network Magic Corporation
401 Kentucky Lane
McKinney, TX 75069
214-793-7757
dnevil@snmc.com
www.snmc.com
quickstack.com
qslinux.org
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-11-10 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 10:35 GDB for host development platform john zhan
2000-11-10 13:55 ` Daris A Nevil [this message]
2000-11-11 7:34 ` john zhan
2000-11-12 23:50 ` Graham Stoney
2000-11-13 15:11 ` Cal Erickson
2000-11-10 16:35 ` Cal Erickson
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=3A0BFE46.A7366165@snmc.com \
--to=dnevil@snmc.com \
--cc=johnzhan@btamail.net.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.