From: Daniel Jacobowitz <drow@false.org>
To: Mitchell Fang <mitchell.fang@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB stub questions
Date: Tue, 31 Jan 2006 18:26:00 -0000 [thread overview]
Message-ID: <20060130202321.GA18495@nevyn.them.org> (raw)
In-Reply-To: <cbd6ac8b0601301216v3bf13577m8678d581d651496c@mail.gmail.com>
On Mon, Jan 30, 2006 at 12:16:07PM -0800, Mitchell Fang wrote:
> I have a question about the GDB stub. Where does the stub run? Is it
> on the host machine, the target board, or the JTAG controller.
This depends on your needs. A stub can typically communicate over TCP
or serial from the stub; over TCP from a stand-alone JTAG unit; or over
TCP on the localhost interface of the host (often talking to a
simulator or a parallel/USB JTAG unit).
If you are using JTAG, it will have to be the second or third of
my listed options; in your case, it sounds like you want the third,
a local daemon.
> Is it possible to edit GDB so that it automatically uses the JTAG
> controller's .dll's directly?
Please do not attempt to do this. We used to add remote targets
directly to GDB; now we are trying to componentize them across the
barrier of the standard remote debug protocol. For one thing,
you end up with tricky-to-maintain code directly in GDB; for another,
the DLLs are often legally encumbered in ways that make linking
them to GDB inadvisable.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-01-30 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 20:23 Mitchell Fang
2006-01-31 18:09 ` Mark Kettenis
2006-01-31 18:26 ` Daniel Jacobowitz [this message]
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=20060130202321.GA18495@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mitchell.fang@gmail.com \
/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