Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Terry Guo <terry.guo@arm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Enable GDB handle compressed target.xml returned by GDB stub
Date: Wed, 27 Jun 2012 21:25:00 -0000	[thread overview]
Message-ID: <4FEB7A27.1030502@eCosCentric.com> (raw)
In-Reply-To: <000601cd5416$e4c21230$ae463690$@guo@arm.com>

On 27/06/12 04:42, Terry Guo wrote:
> Hi Jonathan,
> 
> In terms of transferring the compressed xml file from stub to gdb, I
> find there are two methods:
> 
> 1). Use the original binary format and escape special characters like "$", "#" and "}".
> 2). Convert the original binary format into ASCII format, such as the
> binary format(in hex) "01020304" will be converted into string of bytes
> "01020304"(in ASCII format). The size of binary format is 32 bits while
> the size of string format will be 64 bits (without the NULL terminator).
> The problem is that the binary format is much smaller than the original
> xml file, but after convert, we need to use bigger runtime buffer to store
> the string of bytes.

> So which method will you prefer? I think the method 1) is better.

remote_read_qxfer()/remote_write_qxfer() already do (1) so I don't see any
reason we'd want to allow (2).

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine


      reply	other threads:[~2012-06-27 21:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11  7:31 Terry Guo
2012-06-11 14:43 ` Jonathan Larmour
2012-06-12  9:37   ` Terry Guo
2012-06-12 12:44   ` Yao Qi
2012-06-12 12:57     ` Ulrich Weigand
2012-06-12 16:24       ` Jonathan Larmour
2012-06-13  1:58         ` Terry Guo
2012-06-13 13:42           ` Jonathan Larmour
2012-06-14  0:53             ` Terry Guo
2012-06-13 11:57         ` Terry Guo
2012-06-13 12:26           ` Pedro Alves
2012-06-13 12:51             ` Terry Guo
2012-06-13 13:12               ` Ulrich Weigand
2012-06-13 13:47                 ` Jonathan Larmour
2012-06-14  1:11                   ` Terry Guo
2012-06-14 10:14                 ` Pedro Alves
2012-06-14 13:54                   ` Joel Brobecker
2012-06-14 14:58                     ` Ulrich Weigand
2012-06-14 15:38                   ` Jonathan Larmour
2012-06-19  7:40                     ` Terry Guo
2012-06-22 17:19                       ` Jonathan Larmour
2012-06-26  2:39                         ` Terry Guo
2012-06-26  3:24                         ` Terry Guo
2012-06-26 11:58                           ` Jonathan Larmour
2012-06-27  3:42                             ` Terry Guo
2012-06-27 21:25                               ` Jonathan Larmour [this message]

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=4FEB7A27.1030502@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=gdb-patches@sourceware.org \
    --cc=terry.guo@arm.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