From: Luis Machado <luis.machado@linaro.org>
To: gdb-patches@sourceware.org
Cc: alan.hayward@arm.com, jhb@FreeBSD.org, david.spickett@linaro.org
Subject: [PATCH v2 23/24] Add NEWS entry.
Date: Thu, 22 Oct 2020 17:00:13 -0300 [thread overview]
Message-ID: <20201022200014.5189-24-luis.machado@linaro.org> (raw)
In-Reply-To: <20201022200014.5189-1-luis.machado@linaro.org>
Mention the new packets and memory tagging features.
gdb/ChangeLog:
YYYY-MM-DD Luis Machado <luis.machado@linaro.org>
* NEWS: Mention memory tagging changes.
---
gdb/NEWS | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
diff --git a/gdb/NEWS b/gdb/NEWS
index 1789cf3135..f5c54f1e02 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -23,6 +23,19 @@ show debug event-loop
*** Changes in GDB 10
+* GDB now supports general memory tagging functionality if the underlying
+ architecture supports the proper primitives and hooks. Currently this is
+ enabled only for AArch64 MTE.
+
+ This includes additional information when the inferior crashes with a
+ SIGSEGV caused by a memory tag violation.
+
+* The "x" command supports the 'm' modifier to display allocation tags for
+ a particular memory range.
+
+* The "print" command displays memory tag mismatches for addresses and
+ pointers, if memory tagging is supported by the architecture.
+
* There are new feature names for ARC targets: "org.gnu.gdb.arc.core"
and "org.gnu.gdb.arc.aux". The old names are still supported but
must be considered obsolete. They will be deprecated after some
@@ -105,8 +118,27 @@ show debug event-loop
* On Windows targets, it is now possible to debug 32-bit programs with a
64-bit GDB.
+* New remote packets
+
+qMemTags
+ Request the remote to send allocation tags for a particular memory range.
+QMemTags
+ Request the remote to store the specified allocation tags to the requested
+ memory range.
+
* New commands
+mtag showltag ADDRESS
+ Show the logical tag for ADDRESS.
+mtag setltag ADDRESS TAG
+ Set the logical tag for ADDRESS to TAG.
+mtag showatag ADDRESS
+ Show the allocation tag for ADDRESS.
+mtag setatag ADDRESS LENGTH TAGS
+ Set the allocation tag for [ADDRESS, ADDRESS + LENGTH) to TAGS.
+mtag check ADDRESS
+ Validate that ADDRESS' logical tag matches the allocation tag.
+
set exec-file-mismatch -- Set exec-file-mismatch handling (ask|warn|off).
show exec-file-mismatch -- Show exec-file-mismatch handling (ask|warn|off).
Set or show the option 'exec-file-mismatch'. When GDB attaches to a
--
2.17.1
next prev parent reply other threads:[~2020-10-22 20:02 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 19:59 [PATCH v2 00/24] Memory Tagging Support + AArch64 Linux implementation Luis Machado
2020-10-22 19:59 ` [PATCH v2 01/24] New target methods for memory tagging support Luis Machado
2020-10-27 13:22 ` Simon Marchi
2020-10-27 13:43 ` Luis Machado
2020-10-27 13:50 ` Simon Marchi
2020-10-22 19:59 ` [PATCH v2 02/24] New gdbarch memory tagging hooks Luis Machado
2020-10-22 19:59 ` [PATCH v2 03/24] Add GDB-side remote target support for memory tagging Luis Machado
2020-10-29 14:22 ` Alan Hayward
2020-10-29 14:41 ` Luis Machado
2020-10-22 19:59 ` [PATCH v2 04/24] Unit testing for GDB-side remote memory tagging handling Luis Machado
2020-10-22 19:59 ` [PATCH v2 05/24] GDBserver remote packet support for memory tagging Luis Machado
2020-10-22 19:59 ` [PATCH v2 06/24] Unit tests for gdbserver memory tagging remote packets Luis Machado
2020-10-22 19:59 ` [PATCH v2 07/24] Documentation for " Luis Machado
2020-10-23 6:25 ` Eli Zaretskii
2020-10-23 14:07 ` Luis Machado
2020-10-23 14:33 ` Eli Zaretskii
2020-10-23 14:39 ` Luis Machado
2020-10-22 19:59 ` [PATCH v2 08/24] AArch64: Add MTE CPU feature check support Luis Machado
2020-10-22 19:59 ` [PATCH v2 09/24] AArch64: Add target description/feature for MTE registers Luis Machado
2020-10-22 20:00 ` [PATCH v2 10/24] AArch64: Add MTE register set support for GDB and gdbserver Luis Machado
2020-10-22 20:00 ` [PATCH v2 11/24] AArch64: Add MTE ptrace requests Luis Machado
2020-10-22 20:00 ` [PATCH v2 12/24] AArch64: Implement memory tagging target methods for AArch64 Luis Machado
2020-10-29 14:21 ` Alan Hayward
2020-10-29 14:39 ` Luis Machado
2020-10-29 14:45 ` Luis Machado
2020-10-29 17:32 ` Alan Hayward
2020-10-22 20:00 ` [PATCH v2 13/24] Refactor parsing of /proc/<pid>/smaps Luis Machado
2020-10-22 20:00 ` [PATCH v2 14/24] AArch64: Implement the memory tagging gdbarch hooks Luis Machado
2020-10-22 20:00 ` [PATCH v2 15/24] AArch64: Add unit testing for logical tag set/get operations Luis Machado
2020-10-22 20:00 ` [PATCH v2 16/24] AArch64: Report tag violation error information Luis Machado
2020-10-22 20:00 ` [PATCH v2 17/24] AArch64: Add gdbserver MTE support Luis Machado
2020-10-22 20:00 ` [PATCH v2 18/24] AArch64: Add MTE register set support for core files Luis Machado
2020-10-22 20:00 ` [PATCH v2 19/24] New mtag commands Luis Machado
2020-10-22 20:00 ` [PATCH v2 20/24] Documentation for the new " Luis Machado
2020-10-23 6:35 ` Eli Zaretskii
2020-10-23 14:33 ` Luis Machado
2020-10-23 17:52 ` Eli Zaretskii
2020-10-23 19:04 ` Luis Machado
2020-10-23 19:34 ` Eli Zaretskii
2020-10-26 14:59 ` Luis Machado
2020-10-26 15:35 ` Eli Zaretskii
2020-10-26 16:57 ` Luis Machado
2020-10-22 20:00 ` [PATCH v2 21/24] Extend "x" and "print" commands to support memory tagging Luis Machado
2020-10-22 20:00 ` [PATCH v2 22/24] Document new "x" and "print" memory tagging extensions Luis Machado
2020-10-23 6:37 ` Eli Zaretskii
2020-10-22 20:00 ` Luis Machado [this message]
2020-10-23 6:38 ` [PATCH v2 23/24] Add NEWS entry Eli Zaretskii
2020-10-22 20:00 ` [PATCH v2 24/24] Add memory tagging testcases Luis Machado
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=20201022200014.5189-24-luis.machado@linaro.org \
--to=luis.machado@linaro.org \
--cc=alan.hayward@arm.com \
--cc=david.spickett@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).