Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: James Sampson <i_am_triumph@ofir.dk>
Cc: GDB Archive <gdb@sources.redhat.com>
Subject: Re: Adding a target at build?
Date: Tue, 19 Nov 2002 09:10:00 -0000	[thread overview]
Message-ID: <3DDA7066.9080504@redhat.com> (raw)
In-Reply-To: <20021119151228.729C15C2D7@postfix3.ofir.com>

> Hello Gurus :-)
> 
> Is this understood correctly? :
> 
> When I build the GDB I need to specify a target and a host. The host being the 
> PC I use to run the GDB and the target being the target I wish to debug 
> remotely?.
> 
> If it is :
> 
> Suppose I wish to use a TIC54x target which is supported by the GDB (Me think) 
> - What do I need to do to make this my target at build time?.

As far as I know, no one has implemented a TIC54x target for GDB.
(if it was implemented, it would be configured using something like: 
--target=--target=tic54x).

If you're interested in adding tic54x support to GDB, then have a look 
at the xstormy16 and cris targets.  (You'll also want to arrange an FSF 
copyright assignment so that your work can be included in the official GDB).

> When this is setup, and the GDB's host is different from it's target, does it 
> expect to debug remotely? - Obviously it can't run it on host, because the 
> code is target specific?

Either remotely, or with a built-in simulator.

> Am I way off here?.

nope :-)

Andrew



  reply	other threads:[~2002-11-19 17:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19  6:47 James Sampson
2002-11-19  9:10 ` Andrew Cagney [this message]
2002-11-19 23:19 James Sampson
2002-11-20  6:17 ` Daniel Jacobowitz
2002-11-20  3:47 James Sampson
2002-11-20  7:38 James Sampson
2002-11-20  7:42 ` Daniel Jacobowitz
2002-11-20 11:12 James Sampson

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=3DDA7066.9080504@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=i_am_triumph@ofir.dk \
    /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