public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "Richard Stuckey" <Richard.Stuckey@arc.com>
To: nobody@sources.redhat.com
Cc: gdb-prs@sources.redhat.com,
Subject: RE: remote/2560: valid reponse packet can  be treated as 'ENN'error packet
Date: Tue, 02 Dec 2008 17:28:00 -0000	[thread overview]
Message-ID: <20081202172801.28137.qmail@sourceware.org> (raw)

The following reply was made to PR remote/2560; it has been noted by GNATS.

From: "Richard Stuckey" <Richard.Stuckey@arc.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb-gnats@sources.redhat.com>
Subject: RE: remote/2560: valid reponse packet can  be treated as 'ENN'error packet
Date: Tue, 2 Dec 2008 17:22:38 -0000

 Yes, it was getting a register frame: the first hex digit for the first
 register was 'E' !
 
 Good idea about the lowercase.
 
     Thanks
 
 -----Original Message-----
 From: Daniel Jacobowitz [mailto:drow@false.org]=20
 Sent: 02 December 2008 17:19
 To: Richard Stuckey
 Cc: gdb-gnats@sources.redhat.com
 Subject: Re: remote/2560: valid reponse packet can be treated as
 'ENN'error packet
 
 On Tue, Dec 02, 2008 at 05:04:33PM -0000, richard.stuckey@arc.com wrote:
 > This test is too weak: if the response packet contains valid data
 which happens to begin with an 'E' then it will be incorrectly treated
 as an error.
 
 remote_send is only used in four cases: p/P and g/G.  If you
 encountered it in one of those, I suggest sending back lowercase
 hex rather than uppercase hex.
 
 That does not invalidate your correct report; merely a suggestion.
 
 --=20
 Daniel Jacobowitz
 CodeSourcery
 


             reply	other threads:[~2008-12-02 17:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 17:28 Richard Stuckey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-02 17:28 remote/2560: valid reponse packet can be treated as 'ENN' error packet Daniel Jacobowitz
2008-12-02 17:08 richard.stuckey

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=20081202172801.28137.qmail@sourceware.org \
    --to=richard.stuckey@arc.com \
    --cc=gdb-prs@sources.redhat.com \
    --cc=nobody@sources.redhat.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).