From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 1/2] Allow powerpc-*-lynxos* GDBserver to send register map via XML...
Date: Fri, 04 Jan 2013 21:07:00 -0000 [thread overview]
Message-ID: <50E74475.5070504@redhat.com> (raw)
In-Reply-To: <1355744327-19557-1-git-send-email-brobecker@adacore.com>
On 12/17/2012 11:38 AM, Joel Brobecker wrote:
> ... back to GDB. The transfer occurs when GDB sends the
> 'qXfer:features:read:target.xml' packet. This allows us to make
> sure that GDB and GDBserver use the same register numbering.
> This will be important on Lynx 178, where GDB selects the rs6000:6000
> architecture by default instead of the powerpc:common architecture.
>
> gdb/gdbserver/ChangeLog:
>
> * configure.srv (powerpc-*-lynxos*): Set srv_xmlfiles.
>
> Tested on ppc-lynx5. OK to commit?
Sure.
Note however, that xml descriptions can also send
the OSABI. So if we had new xml descriptions that
did something like:
<!DOCTYPE target SYSTEM "gdb-target.dtd">
<target>
<osabi>Lynx178 (or whatever it is)</osabi>
<xi:include href="..."/>
</target>
and send _that_, then GDB sets the OSABI from
the target, even if you attach without a binary.
This is the modern version of the default OSABI
setting in the end of gdb/configure.tgt, which
I now notice doesn't have a Lynx setting, so
ignore I mentioned it. :-)
--
Pedro Alves
next prev parent reply other threads:[~2013-01-04 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 11:38 Joel Brobecker
2012-12-17 11:38 ` [RFA 2/2] Make x86-lynx GDBserver pass XML register map to GDB Joel Brobecker
2013-01-04 21:07 ` Pedro Alves
2013-01-07 11:54 ` Joel Brobecker
2013-01-04 21:07 ` Pedro Alves [this message]
2013-01-07 11:54 ` [RFA 1/2] Allow powerpc-*-lynxos* GDBserver to send register map via XML Joel Brobecker
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=50E74475.5070504@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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