linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "john zhan" <johnzhan@btamail.net.cn>
To: <linuxppc-embedded@lists.linuxppc.org>
Cc: "Daris A Nevil" <dnevil@snmc.com>,
	"Cal Erickson" <cal_erickson@mvista.com>
Subject: Re: GDB for host development platform
Date: Sat, 11 Nov 2000 15:34:32 +0800	[thread overview]
Message-ID: <00c401c04bb1$dbf78420$57c809c0@fel> (raw)
In-Reply-To: 3A0BFE46.A7366165@snmc.com


Thank you, Daris and Cal, for your reponse.
I believe cross-debugger is good way,no mater the
connection method, serial or Ethernet.
My point is the native debugger targeted exec-file.
The background of my idea is that I will build a new
 ppc system which have all necessary peripheral including
a harddisk, keyboard ,  graphics device and other
standard port.
Base this platform to develop embedded applications,
In fact,I am afraid I will break the traditional development
 mode ,discard the host machine, combine host and  target
 physically, all in one,  like programming in linux/pc.
 I think it can be easy acceptable.
So,I hope GDB can work with exec-file target in a standalone
linux/ppc machine.
It is the worst news that GDB is not ready for linux/ppc exec-file target.
Can someone tell me more about this?
But I can still use GDB targeted extended-remote in native environment.right?

Thanks in advance.

john zhan.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-11-11  7:34 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
2000-11-11  7:34   ` john zhan [this message]
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='00c401c04bb1$dbf78420$57c809c0@fel' \
    --to=johnzhan@btamail.net.cn \
    --cc=cal_erickson@mvista.com \
    --cc=dnevil@snmc.com \
    --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).