public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@linaro.org>
To: Joel Brobecker <brobecker@adacore.com>,
	Simon Marchi <simon.marchi@polymtl.ca>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Luis Machado via Gdb-patches <gdb-patches@sourceware.org>,
	david.spickett@linaro.org
Subject: Re: [PING][PATCH,v5][AArch64] MTE corefile support
Date: Mon, 2 Aug 2021 09:06:00 -0300	[thread overview]
Message-ID: <9f5c7aff-40a3-5d4f-6f2c-b9d9e855916b@linaro.org> (raw)
In-Reply-To: <20210801154405.GA471794@adacore.com>

On 8/1/21 12:44 PM, Joel Brobecker wrote:
>> On 2021-07-29 2:10 p.m., Catalin Marinas wrote:
>>> I'm more worried about GDB 11 reading the MTE notes incorrectly rather
>>> than not reading them at all.
>>
>> Yeah, if a GDB 11 that knows how to read the pre-standardized notes does
>> not fail gracefully when encountering the standardized notes, it would
>> be bad.  If it just skipped them and said "I don't recognize them", it
>> would be ok.
> 
> Agreed.
> 
> Is there a way we could check the notes? I looked at the patch,
> and it doesn't seem like there is any kind of versioning or
> identifier we could use to determine which version of the notes
> we get. But perhaps we can at least do some kind of consistency

We have a generic header containing NT_MEMTAG and an arch-specific 
header identifier containing NT_MEMTAG_TYPE_AARCH_MTE. The arch-specific 
identifier can be versioned as needed. We could, for example, have 
NT_MEMTAG_TYPE_AARCH_MTE_V2.

> check, such as for instance comparing the size of the section
> with the contents of the section header, and generate an error
> if that doesn't match. The error might not be as informative,
> but perhaps still good enough?

On further discussion with the Linux Kernel developers, we're going to 
take the safe path and will wait for this part to be under review on the 
Linux Kernel ML before adopting it in GDB.

> 
>> Oh, ok, I thought it had already gone through some review cycles.  Then
>> I'll leave it to you all to decide, those who have some stakes in this.
> 

  reply	other threads:[~2021-08-02 12:06 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 20:20 [PATCH] [AArch64] " Luis Machado
2021-05-19 10:01 ` David Spickett
2021-05-19 11:11   ` Luis Machado
2021-05-19 12:13 ` Eli Zaretskii
2021-05-21 15:12 ` Alan Hayward
2021-05-21 15:30   ` Luis Machado
2021-05-21 17:20     ` John Baldwin
2021-05-24 13:41       ` Luis Machado
2021-05-24  8:07     ` Alan Hayward
2021-05-24 12:45       ` 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
2021-05-31 14:15   ` [PATCH,v3][AArch64] " Luis Machado
2021-05-31 16:44 ` [PATCH,v4][AArch64] " Luis Machado
2021-06-01 17:45 ` [PATCH,v5][AArch64] " Luis Machado
2021-06-15 14:10   ` [Ping][PATCH,v5][AArch64] " Luis Machado
2021-06-24 14:00   ` [PATCH,v5][AArch64] " Alan Hayward
2021-06-24 14:37     ` Luis Machado
2021-06-24 15:18       ` Alan Hayward
2021-07-01 13:50   ` [PING][PATCH,v5][AArch64] " Luis Machado
2021-07-11 14:22     ` Joel Brobecker
2021-07-14 13:07       ` Catalin Marinas
2021-07-29  2:26         ` Simon Marchi
2021-07-29 16:03           ` John Baldwin
2021-07-29 18:10           ` Catalin Marinas
2021-07-29 18:20             ` Simon Marchi
2021-08-01 15:44               ` Joel Brobecker
2021-08-02 12:06                 ` Luis Machado [this message]
2021-07-19 19:05   ` Luis Machado
2021-07-27 16:10   ` 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=9f5c7aff-40a3-5d4f-6f2c-b9d9e855916b@linaro.org \
    --to=luis.machado@linaro.org \
    --cc=brobecker@adacore.com \
    --cc=catalin.marinas@arm.com \
    --cc=david.spickett@linaro.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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).