From: Daniel Jacobowitz <drow@false.org>
To: Tim Auton <tim.auton@uton.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Remote Debugging Protocol - hex case
Date: Wed, 14 Feb 2007 16:41:00 -0000 [thread overview]
Message-ID: <20070214164125.GA9436@caradoc.them.org> (raw)
In-Reply-To: <B553F6AF-DE2F-412C-8820-CAFABEC34CDC@uton.org>
On Wed, Feb 14, 2007 at 04:25:51PM +0000, Tim Auton wrote:
> OK, I'll have a good look at the testing framework and see what's
> there at
> present.
It won't tell you much. The way I usually test remote protocol work
is by running the whole testsuite using gdbserver - but gdbserver
doesn't implement e.g. the old thread protocol.
> Can I take it that means option 1 looks most desirable?
To me anyway.
> I don't have one, but FSF copyright assignment is no problem to me and
> there's no legal impediment. I presume you'll let me know exactly what
> I need to do to sort the papers out.
Great! I'll send you the form off-list - and thank you very much for
expressing interest in this.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-02-14 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 21:45 Tim Auton
2007-02-13 22:49 ` Daniel Jacobowitz
2007-02-14 16:26 ` Tim Auton
2007-02-14 16:41 ` Daniel Jacobowitz [this message]
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=20070214164125.GA9436@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=tim.auton@uton.org \
/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