From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC 2/9] move some rsp bits into rsp-low.h
Date: Thu, 06 Feb 2014 18:56:00 -0000 [thread overview]
Message-ID: <87ha8c2hox.fsf@fleche.redhat.com> (raw)
In-Reply-To: <52F2A013.8000903@redhat.com> (Pedro Alves's message of "Wed, 05 Feb 2014 20:33:23 +0000")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> Hmm. This makes me a tiny bit nervous. What if some random
Pedro> silly stub out there is checking that the resulting byte after
Pedro> unescaping is one of '#', '$' or '}'? But maybe that's being
Pedro> overzealous...
Naturally we can't rule this out, but I think that, due to the way the
RSP text is written in the manual, it is pretty unlikely:
The binary data representation uses `7d' (ASCII `}') as an escape
character. Any escaped byte is transmitted as the escape character
followed by the original character XORed with `0x20'. For example, the
byte `0x7d' would be transmitted as the two bytes `0x7d 0x5d'. The
bytes `0x23' (ASCII `#'), `0x24' (ASCII `$'), and `0x7d' (ASCII `}')
must always be escaped. Responses sent by the stub must also escape
`0x2a' (ASCII `*'), so that it is not interpreted as the start of a
run-length encoded sequence (described next).
I think it's clear from this that the rule is that any character may be
escaped; and furthermore I think anyone implementing this would tend to
treat it generically.
Pedro> Note this loses i18n in GDB. Please add _().
[...]
Pedro> i18n.
Fixed.
>> $(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
Pedro> Something odd with indentation?
It's pre-existing in the Makefile.
I'll fix it separately in a few.
Tom
next prev parent reply other threads:[~2014-02-06 18:56 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 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
2014-02-06 18:56 ` Tom Tromey [this message]
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: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 3/9] don't let bin2hex call strlen Tom Tromey
2014-02-05 20:36 ` Pedro Alves
2014-01-20 19:23 ` [RFC 4/9] don't let hexify " 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:23 ` [RFC 9/9] update rsp-low comments Tom Tromey
2014-02-05 22:22 ` Pedro Alves
2014-01-20 19:23 ` [RFC 5/9] replace hexify with bin2hex Tom Tromey
2014-02-05 20:38 ` Pedro Alves
2014-01-20 19:38 ` [RFC 7/9] replace unhexify with hex2bin 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=87ha8c2hox.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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