From: Luis Machado <luis.machado@arm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH, v2] [AArch64] MTE corefile support
Date: Fri, 22 Apr 2022 09:12:44 +0100 [thread overview]
Message-ID: <f46481d7-0eef-7433-711c-f969a6bcb202@arm.com> (raw)
In-Reply-To: <83pmlaqvrl.fsf@gnu.org>
Hi Eli,
On 4/21/22 16:52, Eli Zaretskii wrote:
>> Date: Thu, 21 Apr 2022 16:20:40 +0100
>> NoDisclaimer: true
>> From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
>>
>> diff --git a/gdb/NEWS b/gdb/NEWS
>> index 760cb2b7abc..885b3929d84 100644
>> --- a/gdb/NEWS
>> +++ b/gdb/NEWS
>> @@ -3,6 +3,10 @@
>>
>> *** Changes since GDB 12
>>
>> +* GDB now supports dumping memory tag data for AArch64 MTE. It also supports
>> + reading memory tag data for AArch64 MTE from core files generated by
>> + the gcore command or the Linux kernel.
>> +
>
> I think this should say something about the significance of this
> feature. Otherwise it is completely unclear why would GDB want to
> support that.
>
> Same comment for the addition to the manual.
>
> Thanks.
It is a bit short. How about the following additional paragraph?
"When a process uses memory-mapped pages protected by memory tags (for
example, AArch64 MTE), this additional information will be recorded in
the core file in the event of a crash or if GDB generates a core file
from the current process state.
The memory tag data will be used so developers can display the memory
tags from a particular memory region, and will also be used to show a
detailed message about a crash that happened due to a memory tag violation."
next prev parent reply other threads:[~2022-04-22 8:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 14:03 Luis Machado
2022-04-21 15:20 ` [PATCH, v2] " Luis Machado
2022-04-21 15:52 ` Eli Zaretskii
2022-04-22 8:12 ` Luis Machado [this message]
2022-04-22 8:30 ` Eli Zaretskii
2022-04-22 8:37 ` Luis Machado
2022-04-22 8:43 ` Eli Zaretskii
2022-04-22 8:44 ` Luis Machado
2022-04-22 13:27 ` [PATCH 1/2] " Luis Machado
2022-04-22 13:33 ` Eli Zaretskii
2022-04-22 13:30 ` [PATCH, v3] " Luis Machado
2022-05-03 21:56 ` [PATCH, v4] " Luis Machado
2022-05-12 10:36 ` Luis Machado
2022-05-18 12:46 ` Luis Machado
2022-05-18 13:58 ` John Baldwin
2022-05-23 9:50 ` Luis Machado
2022-05-23 9:49 ` Luis Machado
2022-06-06 9:28 ` Luis Machado
2022-06-06 9:42 ` Kuan-Ying Lee
2022-06-06 9:47 ` Luis Machado
2022-06-06 9:54 ` Kuan-Ying Lee
2022-06-06 10:49 ` Eli Zaretskii
2022-06-22 9:04 ` Luis Machado
2022-06-27 14:51 ` Pedro Alves
2022-07-11 10:13 ` Luis Machado
2022-07-11 10:57 ` [PATCH] [AArch64,v5] " Luis Machado
2022-07-18 13:54 ` Pedro Alves
2022-07-19 14:25 ` Luis Machado
-- strict thread matches above, loose matches on Subject: below --
2021-05-18 20:20 [PATCH] [AArch64] " Luis Machado
2021-05-26 14:08 ` [PATCH,v2] " Luis Machado
2021-05-29 3:14 ` Simon Marchi
2021-05-31 14:12 ` Luis Machado
2021-05-31 14:49 ` Simon Marchi
2021-05-31 14:56 ` 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=f46481d7-0eef-7433-711c-f969a6bcb202@arm.com \
--to=luis.machado@arm.com \
--cc=eliz@gnu.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).