From: Andrew Batchelor <A.C.Batchelor-99@student.lboro.ac.uk>
To: Jim Blandy <jimb@redhat.com>
Cc: GDB Newsgroup <gdb@sources.redhat.com>
Subject: Re: GDB --> Parallel Port --> Target??
Date: Fri, 10 Oct 2003 16:49:00 -0000 [thread overview]
Message-ID: <1065804694.1168.9.camel@And.Linux> (raw)
In-Reply-To: <vt2brsrfwf2.fsf@zenia.home>
On Wed, 2003-10-08 at 18:53, Jim Blandy wrote:
> > I may need to do some protocol conversion from the Remote Serial
> > Protocol to something else.
>
> What kind of agent do you have running on the system being debugged
> that will be speaking the protocol with GDB?
Er, I'm not wholly sure yet but I think the target is going to be an ARM
evaluator board with an RV-ICE. This has its own protocol (RV-MSG) so
I'll need to write some sort of protocol converter for GDB.
> GDB's protocol looks really hairy, but there are actually only five or
> six operations you must implement --- the rest are optional. Those
> are:
[.....]
> You can add more and get better behavior, more features, etc. But the
> above are all you need for almost everything --- breakpoints,
> backtraces, expression evaluation, and so on.
Great - thanks for that.
> It's been implemented many times over, and some implementations are
> quite small and simple. See the files called *-stub.c in the GDB
> source tree. Some of them are out-of-date, and none of them are
> really tested or supported, but they'll give you the right idea.
Have I understood this correctly? These stub files are mini-protocol
converters? For the target or can they be adapted for my RV-ICE?
Thanks for your help.
Andy
next prev parent reply other threads:[~2003-10-10 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 10:00 Andrew Batchelor
2003-10-07 16:28 ` Jim Blandy
2003-10-08 13:44 ` Andrew Batchelor
2003-10-08 17:55 ` Jim Blandy
2003-10-10 16:49 ` Andrew Batchelor [this message]
2003-10-10 19:32 ` Jim Blandy
2003-10-08 19:37 ` Andrew Cagney
2003-10-10 16:53 ` Andrew Batchelor
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=1065804694.1168.9.camel@And.Linux \
--to=a.c.batchelor-99@student.lboro.ac.uk \
--cc=gdb@sources.redhat.com \
--cc=jimb@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