From: Andrew Cagney <ac131313@ges.redhat.com>
To: Johan Rydberg <jrydberg@rtmk.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] remote_rcmd
Date: Sun, 14 Jul 2002 09:51:00 -0000 [thread overview]
Message-ID: <3D31A763.7020904@ges.redhat.com> (raw)
In-Reply-To: <20020627035114.M1899@cockmaster.bredbandsbolaget.se>
> Hi,
>
> This small patch adds support for receving more that ~200 bytes
> of output from the "qRcmd" request (ie the monitor command).
>
> I have no idea if this will break any stubs, but hopefully not.
> I don't know how often stubs implement the qRcmd request.
>
> 2002-06-27 Johan Rydberg <jrydberg@rtmk.org>
>
> * remote.c (remote_rcmd): Continue reading output from
> stub until receiving OK.
If I understand this patch correctly, it is changing things so that it
allows:
-> rCmd <command>
<- <HEX-OUTPUT>
<- <HEX-OUTPUT>
<- OK
This is wrong. The target should send:
-> rCmd <command>
<- O <HEX-OUTPUT>
<- O <HEX-OUTPUT>
<- OK
when transfering a longer buffer.
Andrew
> Index: remote.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/remote.c,v
> retrieving revision 1.87
> diff -u -u -r1.87 remote.c
> --- remote.c 15 Jun 2002 22:05:32 -0000 1.87
> +++ remote.c 27 Jun 2002 01:42:02 -0000
> @@ -5210,7 +5210,6 @@
> char c = (fromhex (p[0]) << 4) + fromhex (p[1]);
> fputc_unfiltered (c, outbuf);
> }
> - break;
> }
> }
>
next parent reply other threads:[~2002-07-14 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020627035114.M1899@cockmaster.bredbandsbolaget.se>
2002-07-14 9:51 ` Andrew Cagney [this message]
2002-07-14 10:48 ` Daniel Jacobowitz
2002-07-14 11:00 ` Andrew Cagney
2002-07-14 11:01 ` Daniel Jacobowitz
2002-07-14 17:53 ` Andrew Cagney
2002-07-15 11:49 ` Johan Rydberg
2002-07-15 13:02 ` Andrew Cagney
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=3D31A763.7020904@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jrydberg@rtmk.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