From: Pedro Alves <palves@redhat.com>
To: Juha Aaltonen <turbopultti@gmail.com>,
gdb-mailing list <gdb@sourceware.org>
Subject: Re: Remote response to xmlRegisters?
Date: Thu, 19 Nov 2015 11:24:00 -0000 [thread overview]
Message-ID: <564DB157.3080904@redhat.com> (raw)
In-Reply-To: <CAHR0xd50+-JxYERNC0DGzTPnY11_qFsftKsq1RiUDHqPRGsVBw@mail.gmail.com>
We've already discussed this on IRC, but for the benefit of others
finding this in the archives ...
On 11/18/2015 09:06 AM, Juha Aaltonen wrote:
> What should a remote respond to 'qSupported' that has
> 'xmlRegisters=i386' when remote wants to give its target description?
xmlRegisters=i386 merely serves as indication that gdb understands i386
target descriptions. That was something added in order to allow
stubs/gdbserver to be backwards compatible with older gdb's
that _didn't_ understand i386 target descriptions.
> I obviously didn't respond right, because gdb never asked for the
> target description.
What you need to do is to include 'qXfer:features:read+' in the
stub's qSupported reply, and then implement the qXfer:features:read
packet.
Thanks,
Pedro Alves
prev parent reply other threads:[~2015-11-19 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 9:06 Juha Aaltonen
2015-11-19 11:24 ` Pedro Alves [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=564DB157.3080904@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=turbopultti@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).