From: Keith Seitz <keiths@redhat.com>
To: "Martin M. Hunt" <hunt@redhat.com>
Cc: insight@sources.redhat.com
Subject: Re: [RFC] add gdbserver target
Date: Wed, 09 Oct 2002 12:16:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0210091218180.5478-100000@valrhona.uglyboxes.com> (raw)
In-Reply-To: <200210091150.33420.hunt@redhat.com>
On Wed, 9 Oct 2002, Martin M. Hunt wrote:
> No. It is probably most commonly used for embedded linux cross development.
Ugh. Forgot about that...
> Actually, both gdbserver and libremote don't do downloads and therefore work
> properly with Insight (without using the console) when using the "GDBserver"
> target I added. I really don't want to change the name to
> GDBServer/libremote/rda. Maybe I'll just update the docs?
Yeah, just do whatever you think is best. I don't want to clutter this
dialog any more than need be.
Keith
next prev parent reply other threads:[~2002-10-09 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 10:41 Martin M. Hunt
2002-10-09 10:56 ` Keith Seitz
2002-10-09 11:51 ` Martin M. Hunt
2002-10-09 12:16 ` Keith Seitz [this message]
2002-10-09 17:47 ` Martin M. Hunt
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.0210091218180.5478-100000@valrhona.uglyboxes.com \
--to=keiths@redhat.com \
--cc=hunt@redhat.com \
--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).