From: Andrew Cagney <ac131313@redhat.com>
To: "John S. Yates, Jr." <jyates@netezza.com>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: rsp documentation
Date: Fri, 16 May 2003 14:34:00 -0000 [thread overview]
Message-ID: <3EC4F70D.7000506@redhat.com> (raw)
In-Reply-To: <055001c31bab$6671d6c0$1400a8c0@astral>
> As I mentioned in a mailing yesterday I have been
> implementing thread support in a remote stub.
>
> I had little difficulty implementing the 'P' packet
> but implementing the 'G' packet looked to be a real
> pain. My first cut was to make 'G' return an error.
> Happily my stub work's fine.
>
> Looking at the source in remote.c it is clear that
> the statement in the last sentence of "D.1 Overview"
> in the gdb manual is inaccurate. A stub need not
> implement 'G' if it implements 'P' (at least if it
> is intended to communicate only with more recent
> releases).
Wicked! Can you file a bug report?
Andrew
next prev parent reply other threads:[~2003-05-16 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 13:02 John S. Yates, Jr.
2003-05-16 14:34 ` Andrew Cagney [this message]
2003-05-16 19:11 ` Quality Quorum
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=3EC4F70D.7000506@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jyates@netezza.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).