From: Steve Underwood <steveu@coppice.org>
To: gdb@sources.redhat.com
Subject: Re: rproxy - being maintained?
Date: Wed, 24 Aug 2005 15:57:00 -0000 [thread overview]
Message-ID: <430C98CB.6090302@coppice.org> (raw)
Hi,
>I was looking at http://www.gnu.org/software/gdb/links/
>and at the bottom of the page, it has a link for rproxy (proxy for the
GDB remote protocol), which points to
>http://world.std.com/~qqi/labslave/rproxy.html
<http://world.std.com/%7Eqqi/labslave/rproxy.html> but the only place I
can find this is in google's cache.
>Is rproxy an actively maintained project?
>I noticed that Chris Liechti and Dmitry Diky did a fork, and are now
calling it gdbproxy - but this looked like it was only for the >MSP-430
http://mspgcc.sourceforge.net/tools.html
Actually I was the one who implemented gdbproxy. We needed something for
MSP430 support that would allow us to embed a proprietary library from
TI, and not break licencing rules. I picked up rproxy. I contact its
developer. He has lost interest in the code, so I took it up. I forget
the reason for giving it a new name, but it made sense that the time. :-)
There is nothing MSP430 specific in the code in CVS at
mspgcc.sourceforge.net. What is in there is the generic code, with a
skeleton for a target specific module. The target specific module for
the MSP430 is here with me, and not in CVS. I would welcome anyone using
this code. Its why I put everything I was allowed to in a public CVS
respository.
Regards,
Steve
next reply other threads:[~2005-08-24 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 15:57 Steve Underwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-23 0:16 Robin Getz
2005-08-22 18:01 Robin Getz
2005-08-22 22:58 ` Daniel Jacobowitz
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=430C98CB.6090302@coppice.org \
--to=steveu@coppice.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).