From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: david.spickett@linaro.org
Subject: [PATCH v4 06/25] Unit tests for gdbserver memory tagging remote packets
Date: Wed, 30 Dec 2020 12:38:57 -0300 [thread overview]
Message-ID: <20201230153916.1586725-7-luis.machado@linaro.org> (raw)
In-Reply-To: <20201230153916.1586725-1-luis.machado@linaro.org>
Updates on v4:
- Assert on invalid packet request instead of just returning an error code.
Updates on v2:
- Update unit tests to cope with additional tag type field in the remote
packets.
--
Add some unit testing to exercise the functions handling the qMemTags and
QMemTags packets as well as feature support.
gdbserver/ChangeLog:
YYYY-MM-DD Luis Machado <luis.machado@linaro.org>
* server.cc (test_memory_tagging_functions): New function.
(captured_main): Register test_memory_tagging_functions.
---
gdbserver/server.cc | 78 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 78 insertions(+)
diff --git a/gdbserver/server.cc b/gdbserver/server.cc
index 87b18b819c..9368613c58 100644
--- a/gdbserver/server.cc
+++ b/gdbserver/server.cc
@@ -3644,6 +3644,81 @@ detach_or_kill_for_exit_cleanup ()
}
}
+#if GDB_SELF_TEST
+
+namespace selftests {
+
+static void
+test_memory_tagging_functions (void)
+{
+ /* Setup testing. */
+ gdb::char_vector packet;
+ gdb::byte_vector tags, bv;
+ std::string expected;
+ packet.resize (32000);
+ CORE_ADDR addr;
+ size_t len;
+ int type;
+
+ /* Test parsing a qMemTags request. */
+
+ /* Valid request, addr, len and type updated. */
+ addr = 0xff;
+ len = 255;
+ type = 255;
+ strcpy (packet.data (), "qMemTags:0,0:0");
+ parse_fetch_memtags_request (packet.data (), &addr, &len, &type);
+ SELF_CHECK (addr == 0 && len == 0 && type == 0);
+
+ /* Valid request, addr, len and type updated. */
+ addr = 0;
+ len = 0;
+ type = 0;
+ strcpy (packet.data (), "qMemTags:deadbeef,ff:5");
+ parse_fetch_memtags_request (packet.data (), &addr, &len, &type);
+ SELF_CHECK (addr == 0xdeadbeef && len == 255 && type == 5);
+
+ /* Test creating a qMemTags reply. */
+
+ /* Non-empty tag data. */
+ bv.resize (0);
+
+ for (int i = 0; i < 5; i++)
+ bv.push_back (i);
+
+ expected = "m0001020304";
+ SELF_CHECK (create_fetch_memtags_reply (packet.data (), bv) == true);
+ SELF_CHECK (strcmp (packet.data (), expected.c_str ()) == 0);
+
+ /* Test parsing a QMemTags request. */
+
+ /* Valid request and empty tag data: addr, len, type and tags updated. */
+ addr = 0xff;
+ len = 255;
+ type = 255;
+ tags.resize (5);
+ strcpy (packet.data (), "QMemTags:0,0:0:");
+ SELF_CHECK (parse_store_memtags_request (packet.data (),
+ &addr, &len, tags, &type) == true);
+ SELF_CHECK (addr == 0 && len == 0 && type == 0 && tags.size () == 0);
+
+ /* Valid request and non-empty tag data: addr, len, type
+ and tags updated. */
+ addr = 0;
+ len = 0;
+ type = 0;
+ tags.resize (0);
+ strcpy (packet.data (),
+ "QMemTags:deadbeef,ff:5:0001020304");
+ SELF_CHECK (parse_store_memtags_request (packet.data (), &addr, &len, tags,
+ &type) == true);
+ SELF_CHECK (addr == 0xdeadbeef && len == 255 && type == 5
+ && tags.size () == 5);
+}
+
+} // namespace selftests
+#endif /* GDB_SELF_TEST */
+
/* Main function. This is called by the real "main" function,
wrapped in a TRY_CATCH that handles any uncaught exceptions. */
@@ -3661,6 +3736,9 @@ captured_main (int argc, char *argv[])
bool selftest = false;
#if GDB_SELF_TEST
std::vector<const char *> selftest_filters;
+
+ selftests::register_test ("remote_memory_tagging",
+ selftests::test_memory_tagging_functions);
#endif
current_directory = getcwd (NULL, 0);
--
2.25.1
next prev parent reply other threads:[~2020-12-30 15:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 15:38 [PATCH v4 00/25] Memory Tagging Support + AArch64 Linux implementation Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 01/25] New target methods for memory tagging support Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 02/25] New gdbarch memory tagging hooks Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 03/25] Add GDB-side remote target support for memory tagging Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 04/25] Unit testing for GDB-side remote memory tagging handling Luis Machado via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 05/25] GDBserver remote packet support for memory tagging Luis Machado via Gdb-patches
2020-12-30 15:38 ` Luis Machado via Gdb-patches [this message]
2020-12-30 15:38 ` [PATCH v4 07/25] Documentation for memory tagging remote packets Luis Machado via Gdb-patches
2020-12-30 20:41 ` Eli Zaretskii via Gdb-patches
2020-12-30 15:38 ` [PATCH v4 08/25] AArch64: Add MTE CPU feature check support Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 09/25] AArch64: Add target description/feature for MTE registers Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 10/25] AArch64: Add MTE register set support for GDB and gdbserver Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 11/25] AArch64: Add MTE ptrace requests Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 12/25] AArch64: Implement memory tagging target methods for AArch64 Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 13/25] Convert char array to std::string in linux_find_memory_regions_full Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 14/25] Refactor parsing of /proc/<pid>/smaps Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 15/25] AArch64: Implement the memory tagging gdbarch hooks Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 16/25] AArch64: Add unit testing for logical tag set/get operations Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 17/25] AArch64: Report tag violation error information Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 18/25] AArch64: Add gdbserver MTE support Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 19/25] AArch64: Add MTE register set support for core files Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 20/25] New memory-tag commands Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 21/25] Documentation for the new mtag commands Luis Machado via Gdb-patches
2020-12-30 20:43 ` Eli Zaretskii via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 22/25] Extend "x" and "print" commands to support memory tagging Luis Machado via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 23/25] Document new "x" and "print" memory tagging extensions Luis Machado via Gdb-patches
2020-12-30 20:44 ` Eli Zaretskii via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 24/25] Add NEWS entry Luis Machado via Gdb-patches
2020-12-30 20:45 ` Eli Zaretskii via Gdb-patches
2020-12-30 15:39 ` [PATCH v4 25/25] Add memory tagging testcases Luis Machado via Gdb-patches
2021-01-15 16:02 ` [PATCH v4 00/25] Memory Tagging Support + AArch64 Linux implementation Luis Machado via Gdb-patches
2021-01-26 13:03 ` [PING] " Luis Machado via Gdb-patches
2021-01-26 16:26 ` Simon Marchi via Gdb-patches
2021-01-26 16:36 ` Luis Machado via Gdb-patches
2021-01-26 16:49 ` Simon Marchi via Gdb-patches
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=20201230153916.1586725-7-luis.machado@linaro.org \
--to=gdb-patches@sourceware.org \
--cc=david.spickett@linaro.org \
--cc=luis.machado@linaro.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