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

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.

BR,
Terry

> -----Original Message-----
> From: Jonathan Larmour [mailto:jifl@ecoscentric.com]
> Sent: Tuesday, June 26, 2012 7:58 PM
> To: Terry Guo
> Cc: 'Pedro Alves'; 'Ulrich Weigand'; 'Yao Qi'; gdb-
> patches@sourceware.org; tromey@redhat.com; Richard Earnshaw; Joey Ye;
> Matthew Gretton-Dann
> Subject: Re: [RFC] Enable GDB handle compressed target.xml returned by
> GDB stub
> 
> Terry Guo wrote:
> > Hi Jonathan,
> >
> > I read your email again and think your solution is:
> >
> >   If stub doesn't return compressedXML+ then
> >     We go with plain read
> >   Else we go with compressed read
> >      If we get NUL reply
> >         Then we fall back to plain read
> >
> > If this time my understanding on your solution is correct, I think it
> > does save effort on round trip by not always round trip.
> 
> Yes, that's what I was proposing.
> 
> By the way, there are a lot of people on CC for this thread, and I
> don't
> know if they ought to be. Send me and Terry a direct note if you want
> off
> CC - I've just been preserving the CCs.
> 
> 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  3:42 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 [this message]
2012-06-27 21:25                               ` Jonathan Larmour

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='000601cd5416$e4c21230$ae463690$@guo@arm.com' \
    --to=terry.guo@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jifl@ecoscentric.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