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: 'Pedro Alves' <palves@redhat.com>,
	 'Ulrich Weigand' <uweigand@de.ibm.com>,
	'Yao Qi' <yao@codesourcery.com>,
	 gdb-patches@sourceware.org,  tromey@redhat.com,
	Richard Earnshaw <Richard.Earnshaw@arm.com>,
	 Joey Ye <Joey.Ye@arm.com>,
	Matthew Gretton-Dann <Matthew.Gretton-Dann@arm.com>
Subject: Re: [RFC] Enable GDB handle compressed target.xml returned by GDB stub
Date: Tue, 26 Jun 2012 11:58:00 -0000	[thread overview]
Message-ID: <4FE9A3DA.30504@eCosCentric.com> (raw)
In-Reply-To: <000301cd534b$3dd1e1b0$b975a510$@guo@arm.com>

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-26 11:58 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 [this message]
2012-06-27  3:42                             ` Terry Guo
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=4FE9A3DA.30504@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=Joey.Ye@arm.com \
    --cc=Matthew.Gretton-Dann@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=terry.guo@arm.com \
    --cc=tromey@redhat.com \
    --cc=uweigand@de.ibm.com \
    --cc=yao@codesourcery.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