Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Batchelor <A.C.Batchelor-99@student.lboro.ac.uk>
To: Bill Gatliff <bgat@billgatliff.com>
Cc: GDB Newsgroup <gdb@sources.redhat.com>
Subject: Re: Protocol Translation (Apologies for LONG email)
Date: Wed, 11 Feb 2004 22:12:00 -0000	[thread overview]
Message-ID: <1076537572.1123.892.camel@And.Linux> (raw)
In-Reply-To: <402A32C3.1000506@billgatliff.com>

Hi Bill,

Thanks for your reply...

On Wed, 2004-02-11 at 13:48, Bill Gatliff wrote:
> Could you make a gdbserver-like proxy utility, that would launch before 
> gdb and listen on a port on localhost?  Gdb would then connect to that 
> port with RSP (or RDI or whatever), and you could translate the incoming 
> messages to whatever protocol you needed on the ICE end.

Hmmm, good idea, I'd not thought of that.  I've not really looked at the
gdbserver code, so I think I'll have a dig around in the morning.  It
sounds like what I'm after...

> Your server program could parse a configuration file, which might 
> contain instructions to download the application to the target before 
> gdb connects, or other housekeeping matters.

I'm not sure I understand you here, "parse a configuration file"?

> Once connected, you could use gdb's "maintenance" commands to send 
> out-of-band messages for the things that don't translate well between 
> RSP and your target protocol.

Do all GDB messages go via the gdbserver?

> This is not unlike how gdbserver, the BDI2000, and some versions of the 
> Wiggler work, and it wouldn't require modification of a single line of 
> gdb source code.

That's a plus.  I'm still flip-flopping between actually adding-IN to
the GDB code or (like this) adding-ON to it.

Thanks again for your help.


Andrew


  reply	other threads:[~2004-02-11 22:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-11 13:33 Ramana Radhakrishnan
2004-02-11 13:48 ` Bill Gatliff
2004-02-11 22:12   ` Andrew Batchelor [this message]
2004-02-11 22:12 ` Andrew Batchelor
  -- strict thread matches above, loose matches on Subject: below --
2004-02-11 13:11 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=1076537572.1123.892.camel@And.Linux \
    --to=a.c.batchelor-99@student.lboro.ac.uk \
    --cc=bgat@billgatliff.com \
    --cc=gdb@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