From: Tom Tromey <tom@tromey.com>
To: Gustavo Romero <gustavo.romero@linaro.org>
Cc: gdb-patches@sourceware.org, luis.machado@arm.com,
thiago.bauermann@linaro.org
Subject: Re: [PATCH v3 7/7] gdb: Document qMemTagCheckAddr packet
Date: Mon, 08 Apr 2024 13:37:23 -0600 [thread overview]
Message-ID: <87msq363yk.fsf@tromey.com> (raw)
In-Reply-To: <20240404064819.2848899-8-gustavo.romero@linaro.org> (Gustavo Romero's message of "Thu, 4 Apr 2024 06:48:19 +0000")
>>>>> "Gustavo" == Gustavo Romero <gustavo.romero@linaro.org> writes:
Gustavo> +@item @w{}
Gustavo> +An empty reply indicates that @samp{qMemTagCheckAddr} is not supported by the
Gustavo> +stub. This situation should not occur because @value{GDBN} will only send this
Gustavo> +packet if the stub has advertised support for memory tagging check via the
Gustavo> +@samp{memory-tagging-check-addr} feature in @samp{qSupported}.
Is querying really needed in this case?
Like, if there is some user feature that requires knowing whether this
work before ever trying it, then I guess that would be a good
justification. In other cases, it seems to me that simply trying to use
a packet is better than a qSupported response; or at least I don't know
why it wouldn't be.
Tom
next prev parent reply other threads:[~2024-04-08 19:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 6:48 [PATCH v3 0/7] Add another way to check tagged addresses on remote targets Gustavo Romero
2024-04-04 6:48 ` [PATCH v3 1/7] gdb: aarch64: Remove MTE address checking from get_memtag Gustavo Romero
2024-04-04 14:11 ` Luis Machado
2024-04-04 6:48 ` [PATCH v3 2/7] gdb: aarch64: Move MTE address check out of set_memtag Gustavo Romero
2024-04-04 14:17 ` Luis Machado
2024-04-06 23:07 ` Gustavo Romero
2024-04-04 6:48 ` [PATCH v3 3/7] gdb: aarch64: Remove MTE address checking from memtag_matches_p Gustavo Romero
2024-04-04 14:19 ` Luis Machado
2024-04-04 6:48 ` [PATCH v3 4/7] gdb: Use passed gdbarch instead of calling current_inferior Gustavo Romero
2024-04-04 14:20 ` Luis Machado
2024-04-04 6:48 ` [PATCH v3 5/7] gdb: Introduce is_address_tagged target hook Gustavo Romero
2024-04-04 15:45 ` Luis Machado
2024-04-04 16:12 ` Gustavo Romero
2024-04-04 16:20 ` Luis Machado
2024-04-08 20:47 ` Gustavo Romero
2024-04-04 6:48 ` [PATCH v3 6/7] gdb: Add qMemTagAddrCheck packet Gustavo Romero
2024-04-04 16:18 ` Luis Machado
2024-04-04 6:48 ` [PATCH v3 7/7] gdb: Document qMemTagCheckAddr packet Gustavo Romero
2024-04-04 7:40 ` Eli Zaretskii
2024-04-08 19:37 ` Tom Tromey [this message]
2024-04-09 13:23 ` Gustavo Romero
2024-04-09 15:33 ` Tom Tromey
2024-04-09 15:52 ` 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=87msq363yk.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=gustavo.romero@linaro.org \
--cc=luis.machado@arm.com \
--cc=thiago.bauermann@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).