From: Stafford Horne <shorne@gmail.com>
To: GDB patches <gdb-patches@sourceware.org>
Cc: Stafford Horne <shorne@gmail.com>
Subject: [PATCH 1/3] reggroups: Add test and docs for `info reg $reggroup` feature
Date: Wed, 07 Jun 2017 22:16:00 -0000 [thread overview]
Message-ID: <83413241fe0897c873b1cc6e18ccbec78a7a2a25.1496871270.git.shorne@gmail.com> (raw)
In-Reply-To: <cover.1496871270.git.shorne@gmail.com>
In-Reply-To: <cover.1496871270.git.shorne@gmail.com>
Until now this feature has existed but was not documented. Adding docs
and tests.
gdb/ChangeLog:
2017-06-06 Stafford Horne <shorne@gmail.com>
* doc/gdb.texinfo: Document info reg $reggroup feature.
gdb/testsuite/ChangeLog:
2017-06-06 Stafford Horne <shorne@gmail.com>
* gdb.base/reggroups.c: New file.
* gdb.base/reggroups.exp: New file.
---
gdb/doc/gdb.texinfo | 5 +++
gdb/testsuite/gdb.base/reggroups.c | 4 ++
gdb/testsuite/gdb.base/reggroups.exp | 71 ++++++++++++++++++++++++++++++++++++
3 files changed, 80 insertions(+)
create mode 100644 gdb/testsuite/gdb.base/reggroups.c
create mode 100644 gdb/testsuite/gdb.base/reggroups.exp
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 9fb70f6..a11db0c 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -10878,6 +10878,11 @@ and vector registers (in the selected stack frame).
Print the names and values of all registers, including floating-point
and vector registers (in the selected stack frame).
+@item info registers @var{reggroup} @dots{}
+Print the name and value of the restiers in each of the specified
+@var{reggroup}. The @var{reggoup} can be any of those returned by
+@code{maint print reggroups}.
+
@item info registers @var{regname} @dots{}
Print the @dfn{relativized} value of each specified register @var{regname}.
As discussed in detail below, register values are normally relative to
diff --git a/gdb/testsuite/gdb.base/reggroups.c b/gdb/testsuite/gdb.base/reggroups.c
new file mode 100644
index 0000000..f8b643a
--- /dev/null
+++ b/gdb/testsuite/gdb.base/reggroups.c
@@ -0,0 +1,4 @@
+int main()
+{
+ return 0;
+}
diff --git a/gdb/testsuite/gdb.base/reggroups.exp b/gdb/testsuite/gdb.base/reggroups.exp
new file mode 100644
index 0000000..fd51c50
--- /dev/null
+++ b/gdb/testsuite/gdb.base/reggroups.exp
@@ -0,0 +1,71 @@
+# This testcase is part of GDB, the GNU debugger.
+
+# Copyright 2014-2017 Free Software Foundation, Inc.
+
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+# Test listing reggroups and the registers in each group.
+
+standard_testfile
+
+if {[prepare_for_testing "failed to prepare" $testfile $srcfile debug]} {
+ return -1
+}
+
+if ![runto_main] then {
+ fail "can't run to main"
+ return 0
+}
+
+proc fetch_reggroups {test} {
+ global gdb_prompt
+ global expect_out
+
+ set reggroups {}
+ set bad -1
+ gdb_test_multiple "maint print reggroups" "get reggroups" {
+ -re "maint print reggroups\r\n" {
+ exp_continue
+ }
+ -re "^ Group\[ \t\]+Type\[ \t\]+\r\n" {
+ exp_continue
+ }
+ -re "^ (\[0-9a-zA-Z\-\]+)\[ \t\]+(user|internal)\[ \t\]+\r\n" {
+ lappend reggroups $expect_out(1,string)
+ exp_continue
+ }
+ -re ".*$gdb_prompt $" {
+ if { [llength $reggroups] != 0 } {
+ incr bad
+ } else {
+ set bad 1
+ }
+ }
+ }
+
+ if {$bad} {
+ fail $test
+ return {}
+ }
+
+ pass $test
+ return $reggroups
+}
+
+set reggroups [fetch_reggroups "fetch reggroups"]
+set reggroup ""
+
+foreach reggroup [lrange $reggroups 0 end] {
+ gdb_test "info reg $reggroup" ".*" "info reg $reggroup"
+}
--
2.9.4
next prev parent reply other threads:[~2017-06-07 22:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 22:15 [PATCH 0/3] Support for arbitrary reggroups Stafford Horne
2017-06-07 22:16 ` [PATCH 3/3] tdesc: handle arbitrary strings in tdesc_register_in_reggroup_p Stafford Horne
2017-06-08 2:40 ` Eli Zaretskii
2017-06-08 5:01 ` Stafford Horne
2017-06-08 14:56 ` Eli Zaretskii
2017-06-08 20:52 ` Simon Marchi
2017-06-09 11:45 ` Stafford Horne
2017-06-09 19:59 ` Simon Marchi
2017-06-10 8:17 ` Stafford Horne
2017-06-13 11:17 ` Pedro Alves
2017-06-07 22:16 ` Stafford Horne [this message]
2017-06-08 2:38 ` [PATCH 1/3] reggroups: Add test and docs for `info reg $reggroup` feature Eli Zaretskii
2017-06-08 4:59 ` Stafford Horne
2017-06-08 20:31 ` Simon Marchi
2017-06-08 23:27 ` Stafford Horne
2017-06-09 6:20 ` Simon Marchi
2017-06-13 11:17 ` Pedro Alves
2017-06-07 22:16 ` [PATCH 2/3] reggroups: Convert reggroups from post_init to pre_init Stafford Horne
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=83413241fe0897c873b1cc6e18ccbec78a7a2a25.1496871270.git.shorne@gmail.com \
--to=shorne@gmail.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