From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: yao@codesourcery.com (Yao Qi)
Cc: jifl@eCosCentric.com (Jonathan Larmour),
terry.guo@arm.com (Terry Guo),
gdb-patches@sourceware.org, tromey@redhat.com,
Richard.Earnshaw@arm.com (Richard Earnshaw),
palves@redhat.com ('Pedro Alves'),
Joey.Ye@arm.com (Joey Ye)
Subject: Re: [RFC] Enable GDB handle compressed target.xml returned by GDB stub
Date: Tue, 12 Jun 2012 12:57:00 -0000 [thread overview]
Message-ID: <201206121256.q5CCua79003559@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <4FD73977.4050702@codesourcery.com> from "Yao Qi" at Jun 12, 2012 08:43:35 PM
Yao Qi wrote:
> On 06/11/2012 10:42 PM, Jonathan Larmour wrote:
> > It may want some variation on the qSupported "qXfer:features:read"
> > response instead. I'll defer to GDB maintainers in the choice, but perhaps
> > qXfer:features:zread ?
>
> I'd like GDB keeps using qXfer:features:read:target.xml to fetch the xml
> file, even it is compressed. We need some changes on qSupported in both
> sides,
That still makes the result of qXfer:features:read:target.xml dependent
on global state ... Why not simply support compressed files by having
the stub respond to
qXfer:features:read:target.xml.gz
(etc) if it has a compressed file image?
Optionally we might still add a qSupported feature as you describe;
otherwise GDB might just probe whether the stub knows .gz files.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2012-06-12 12:57 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 [this message]
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
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=201206121256.q5CCua79003559@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=Joey.Ye@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=jifl@eCosCentric.com \
--cc=palves@redhat.com \
--cc=terry.guo@arm.com \
--cc=tromey@redhat.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