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 18:31:47 -0500 (EST)
- cc: gdb at sourceware dot cygnus dot com
On Wed, 15 Dec 1999, Andrew Cagney wrote:
> Quality Quorum wrote:
> >
> > 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.
>
> Sorry, to late.
Then it has to be depreciated right away - it is broken in too many
places and it is not going to ever work correctly anyway.
And again we can cover it be variable, say - 'brokenqrcmd'
> Technically it is the ``OOUTPUT'' bit that shouldn't be
> there. Only the qRcmd packet supports it. However, I do see your
> point.
>
> Andrew
>
Thanks,
Aleksey