* Remote response to xmlRegisters?
@ 2015-11-18 9:06 Juha Aaltonen
2015-11-19 11:24 ` Pedro Alves
0 siblings, 1 reply; 2+ messages in thread
From: Juha Aaltonen @ 2015-11-18 9:06 UTC (permalink / raw)
To: gdb-mailing list
What should a remote respond to 'qSupported' that has
'xmlRegisters=i386' when remote wants to give its target description?
I obviously didn't respond right, because gdb never asked for the
target description.
Also, does gdb-multiarch know target descriptions, and if, can
response refer to that? Like 'xmlRegisters=org.gnu.gdb.arm.neon" or
similar?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Remote response to xmlRegisters?
2015-11-18 9:06 Remote response to xmlRegisters? Juha Aaltonen
@ 2015-11-19 11:24 ` Pedro Alves
0 siblings, 0 replies; 2+ messages in thread
From: Pedro Alves @ 2015-11-19 11:24 UTC (permalink / raw)
To: Juha Aaltonen, gdb-mailing list
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-11-19 11:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-11-18 9:06 Remote response to xmlRegisters? Juha Aaltonen
2015-11-19 11:24 ` Pedro Alves
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).