This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: remote nits
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: remote nits
- From: Quality Quorum <qqi at world dot std dot com>
- Date: Tue, 14 Dec 1999 11:09:08 -0500 (EST)
- cc: gdb at sourceware dot cygnus dot com
On Wed, 15 Dec 1999, Andrew Cagney wrote:
> Quality Quorum wrote:
> >
> >
> > ???????? As far as I understand the document normal response to
> > Rcmd is a sequence of zero of more 'O' packets followed, by OK or 'ENN'.
>
> One of the specified return codes is:
>
> reply OUTPUT
> A command response with the hex encoded output string OUTPUT.
This one should be outlawed before it is too late, it simply does not
make any sense.
> > and is separate to in intermediate O packet.
> > > IMHO, the only use of Rcmd is to allow user to type some command
> > and see the response, in all other cases query should be defined and
> > used not a command, we have raw queries just for this purpose.
>
> Sorry you've lost me here.
The question is who is going to issue a command and to interpret a command
response ?
If it is a user then proper response have to be in user-readable
form ('O' packet). If it is machine, then command query should not be
used (we have raw queries for the purpose).
>
> Andrew
>
Thanks,
Aleksey