[22/23] Add NEWS entry.

Message ID 20200715194513.16641-23-luis.machado@linaro.org
State New
Headers show
Series
  • Memory Tagging Support + AArch64 Linux implementation
Related show

Commit Message

Eli Zaretskii via Gdb-patches July 15, 2020, 7:45 p.m.
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(+)

-- 
2.17.1

Comments

Eli Zaretskii July 17, 2020, 6:18 a.m. | #1
> Date: Wed, 15 Jul 2020 16:45:12 -0300

> From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>

> Cc: catalin.marinas@arm.com, david.spickett@linaro.org

> 

> +* The "x" command supports the 'm' modifier to display allocation tags for

> +  a particular memory range.

> +

> +* The "print" command will display memory tag mismatches for addresses and

> +  pointers, if memory tagging is supported by the architecture.


"Supports" vs "will display".  Please use "displays" in the latter.

This part is OK with that nit fixed, thanks.
Eli Zaretskii via Gdb-patches July 17, 2020, 2:20 p.m. | #2
On 7/17/20 3:18 AM, Eli Zaretskii wrote:
>> Date: Wed, 15 Jul 2020 16:45:12 -0300

>> From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>

>> Cc: catalin.marinas@arm.com, david.spickett@linaro.org

>>

>> +* The "x" command supports the 'm' modifier to display allocation tags for

>> +  a particular memory range.

>> +

>> +* The "print" command will display memory tag mismatches for addresses and

>> +  pointers, if memory tagging is supported by the architecture.

> 

> "Supports" vs "will display".  Please use "displays" in the latter.

> 

> This part is OK with that nit fixed, thanks.

> 


Thanks. I've addressed these locally now.

Patch

diff --git a/gdb/NEWS b/gdb/NEWS
index ded544d640..42e719417f 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -3,6 +3,19 @@ 
 
 *** Changes since GDB 9
 
+* 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 will display memory tag mismatches for addresses and
+  pointers, if memory tagging is supported by the architecture.
+
 * Help and apropos commands will now show the documentation of a
   command only once, even if that command has one or more aliases.
   These commands now show the command name, then all of its aliases,
@@ -63,8 +76,27 @@ 
 * 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