From: Andrew Sutherland <sombrero@alum.mit.edu>
To: archer@sourceware.org
Subject: Re: regression in remote.c in remote_threads_info for qfThreadInfo/qsThreadInfo with the introduction of read_ptid
Date: Thu, 10 Sep 2009 21:52:00 -0000 [thread overview]
Message-ID: <h8bsed$5ui$1@ger.gmane.org> (raw)
In-Reply-To: <200909101111.25154.pedro@codesourcery.com>
On 09/10/2009 03:11 AM, Pedro Alves wrote:
> "Like the descriptions of the other packets, each description here has a template showing the packet's
> overall syntax, followed by an explanation of the packet's meaning. We include spaces in some of the
> templates for clarity; these are not part of the packet's syntax. No GDB packet uses
> spaces to separate its components."
I did miss that, thank you. And it certainly does make sense to not
include whitespace in a machine protocol...
Is there any form of policy on backwards compatibility for the remote
debugging protocol? The problematic gdb stub is the VMware stub (as
found in Workstation 6.x), and when notifying them of this problem, it'd
be good to know how much of a problem it in fact is.
Thanks,
Andrew
next prev parent reply other threads:[~2009-09-10 21:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 5:25 Andrew Sutherland
2009-09-10 10:11 ` Pedro Alves
2009-09-10 21:52 ` Andrew Sutherland [this message]
2009-09-11 14:36 ` Pedro Alves
2009-09-11 14:39 ` Pedro Alves
2009-09-11 22:48 ` Tom Tromey
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='h8bsed$5ui$1@ger.gmane.org' \
--to=sombrero@alum.mit.edu \
--cc=archer@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).