From: Keith Seitz <keiths@redhat.com>
To: Masahide Tomita <fsi_tomi@bcpc601.neec.abk.nec.co.jp>
Cc: insight@sources.redhat.com
Subject: Re: Remote debug using Insight
Date: Thu, 03 Oct 2002 08:40:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0210030835230.1509-100000@valrhona.uglyboxes.com> (raw)
In-Reply-To: <009d01c26a9c$ddc96140$41dc280a@ABKNEECBCPCD65>
On Thu, 3 Oct 2002, Masahide Tomita wrote:
> I am quite new here in this ML, and in using Insight(gdb too.).
Welcome.
> My question is: How do I use Insight to debug program running on remote
> host?
Ok, there are a bunch of questions to which you must know the answer in
order to debug a remote target:
What's the communications protocol?
This is the actual hardware communications between the host (running
gdb/insight) and the target. Is it a serial connection? Ethernet? JTAG?
For serial, you'll need to know what serial port the target is attached to
and the baud rate. For ethernet, you'll need a hostname/IP address and
port number. If you're using a JTAG box, you'll obviously need to know
these parameters for the interface, not for the board proper, since GDB
will be talking to the JTAG interface.
What's the debug protocol?
This could be the tougher one. GDB understands how to talk a bunch of
different debug protocols, its own "remote" protocol, many monitors, a
couple of JTAG, etc.
On this one, I don't know how to help you out. You're going to have to
find out what the board uses (if anything). Maybe you'll need to get a GDB
debug stub/agent on the board? I don't know. You might ask on
gdb@sources.redhat.com about your particular hardware if web searches
don't turn anything up.
Anyway, once you have this information, you can use the File->Target
Settings... dialog to specify these things.
Keith
next prev parent reply other threads:[~2002-10-03 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 22:22 Masahide Tomita
2002-10-03 8:40 ` Keith Seitz [this message]
2002-10-03 8:54 ` multi-threaded debugging " Bruce Korb
2002-10-03 9:01 ` Keith Seitz
2002-10-03 10:28 ` Bruce Korb
2002-10-03 10:35 ` Keith Seitz
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=Pine.LNX.4.44.0210030835230.1509-100000@valrhona.uglyboxes.com \
--to=keiths@redhat.com \
--cc=fsi_tomi@bcpc601.neec.abk.nec.co.jp \
--cc=insight@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).