From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: [RFA 1/2] Allow powerpc-*-lynxos* GDBserver to send register map via XML...
Date: Mon, 17 Dec 2012 11:38:00 -0000 [thread overview]
Message-ID: <1355744327-19557-1-git-send-email-brobecker@adacore.com> (raw)
... 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?
Thanks,
--
Joel
---
gdb/gdbserver/configure.srv | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/gdb/gdbserver/configure.srv b/gdb/gdbserver/configure.srv
index d1e04a9..cb7cfee 100644
--- a/gdb/gdbserver/configure.srv
+++ b/gdb/gdbserver/configure.srv
@@ -229,6 +229,9 @@ case "${target}" in
;;
powerpc-*-lynxos*) srv_regobj="powerpc-32.o"
srv_tgtobj="lynx-low.o lynx-ppc-low.o"
+ srv_xmlfiles="rs6000/powerpc-32.xml"
+ srv_xmlfiles="${srv_xmlfiles} rs6000/power-core.xml"
+ srv_xmlfiles="${srv_xmlfiles} rs6000/power-fpu.xml"
srv_lynxos=yes
;;
s390*-*-linux*) srv_regobj="s390-linux32.o"
--
1.7.0.4
next reply other threads:[~2012-12-17 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 11:38 Joel Brobecker [this message]
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 ` [RFA 1/2] Allow powerpc-*-lynxos* GDBserver to send register map via XML Pedro Alves
2013-01-07 11:54 ` 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=1355744327-19557-1-git-send-email-brobecker@adacore.com \
--to=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