Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC 2/9] move some rsp bits into rsp-low.h
Date: Wed, 05 Feb 2014 20:33:00 -0000	[thread overview]
Message-ID: <52F2A013.8000903@redhat.com> (raw)
In-Reply-To: <1390245501-1186-3-git-send-email-tromey@redhat.com>

On 01/20/2014 07:18 PM, Tom Tromey wrote:
> This moves various low-level remote serial protocol bits into
> common/rsp-low.[ch].
> 
> This is as close to a pure move as possible.  There are some
> redundancies remaining but those will be dealt with in a subsequent
> patch.
> 
> Note that the two variants of remote_escape_output disagreed on the
> treatment of "*".  On the theory that quoting cannot hurt but the
> absence possibly can, I chose the gdbserver variant to be the
> canonical one.

Hmm.  This makes me a tiny bit nervous.  What if some random
silly stub out there is checking that the resulting byte after
unescaping is one of '#', '$' or '}'?  But maybe that's being
overzealous...

> +int
> +remote_unescape_input (const gdb_byte *buffer, int len,
> +		       gdb_byte *out_buf, int out_maxlen)
> +{
> +  int input_index, output_index;
> +  int escaped;
> +
> +  output_index = 0;
> +  escaped = 0;
> +  for (input_index = 0; input_index < len; input_index++)
> +    {
> +      gdb_byte b = buffer[input_index];
> +
> +      if (output_index + 1 > out_maxlen)
> +	error ("Received too much data from the target.");

Note this loses i18n in GDB.  Please add _().  Also, in
the GDB this particular error was actually warning, but
I think it's fine to make it an error.  I also notice that
"target" in "from the target" isn't right in the gdbserver
case, but that's a preexisting minor issue.

> +
> +      if (escaped)
> +	{
> +	  out_buf[output_index++] = b ^ 0x20;
> +	  escaped = 0;
> +	}
> +      else if (b == '}')
> +	escaped = 1;
> +      else
> +	out_buf[output_index++] = b;
> +    }
> +
> +  if (escaped)
> +    error ("Unmatched escape character in target response.");

i18n.

> +
> +  return output_index;
> +}
> +


> @@ -163,7 +163,8 @@ SFILES=	$(srcdir)/gdbreplay.c $(srcdir)/inferiors.c $(srcdir)/dll.c \
>  	$(srcdir)/common/linux-osdata.c $(srcdir)/common/ptid.c \
>  	$(srcdir)/common/buffer.c $(srcdir)/common/linux-btrace.c \
>  	$(srcdir)/common/filestuff.c $(srcdir)/target/waitstatus.c \
> -    $(srcdir)/common/mips-linux-watch.c $(srcdir)/common/cells.c
> +    $(srcdir)/common/mips-linux-watch.c $(srcdir)/common/cells.c \
> +	$(srcdir)/common/rsp-low.c

Something odd with indentation?

Otherwise, this looks fine to me.

-- 
Pedro Alves


  parent reply	other threads:[~2014-02-05 20:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 19:18 [RFC 0/9] move more code into common/ Tom Tromey
2014-01-20 19:18 ` [RFC 3/9] don't let bin2hex call strlen Tom Tromey
2014-02-05 20:36   ` Pedro Alves
2014-01-20 19:18 ` [RFC 1/9] share "cell" code Tom Tromey
2014-02-05 20:05   ` Pedro Alves
2014-02-05 20:13     ` Tom Tromey
2014-02-06  2:28       ` Yao Qi
2014-02-06 18:51         ` Tom Tromey
2014-01-20 19:18 ` [RFC 2/9] move some rsp bits into rsp-low.h Tom Tromey
2014-01-21  3:24   ` Yao Qi
2014-02-05 20:33   ` Pedro Alves [this message]
2014-02-06 18:56     ` Tom Tromey
2014-02-06 19:08       ` Pedro Alves
2014-01-20 19:18 ` [RFC 6/9] replace convert_int_to_ascii with bin2hex Tom Tromey
2014-02-05 20:39   ` Pedro Alves
2014-01-20 19:23 ` [RFC 5/9] replace hexify " Tom Tromey
2014-02-05 20:38   ` Pedro Alves
2014-01-20 19:23 ` [RFC 9/9] update rsp-low comments Tom Tromey
2014-02-05 22:22   ` Pedro Alves
2014-01-20 19:23 ` [RFC 4/9] don't let hexify call strlen Tom Tromey
2014-02-05 20:37   ` Pedro Alves
2014-01-20 19:23 ` [RFC 8/9] replace convert_ascii_to_int with hex2bin Tom Tromey
2014-02-05 22:18   ` Pedro Alves
2014-01-20 19:38 ` [RFC 7/9] replace unhexify " Tom Tromey
2014-02-05 22:14   ` Pedro Alves

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=52F2A013.8000903@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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