From: Eli Zaretskii <eliz@gnu.org>
To: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] doc: add the missing 'handle' attribute in xml
Date: Tue, 02 Apr 2024 15:14:11 +0300 [thread overview]
Message-ID: <86jzlg9d2k.fsf@gnu.org> (raw)
In-Reply-To: <20240402102020.2521082-1-tankut.baris.aktemur@intel.com> (message from Tankut Baris Aktemur on Tue, 2 Apr 2024 12:20:19 +0200)
> From: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
> Date: Tue, 2 Apr 2024 12:20:19 +0200
>
> The XML response to the "qXfer:threads:read" packet may include
> a "handle" attribute. The attribute is mentioned in the document
> but not shown in the sample XML structure. Add it.
> ---
> gdb/doc/gdb.texinfo | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 727f9275bfb..41a368a0194 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -48081,7 +48081,7 @@ the following structure:
> @smallexample
> <?xml version="1.0"?>
> <threads>
> - <thread id="id" core="0" name="name">
> + <thread id="id" core="0" name="name" handle="XX...">
> ... description ...
> </thread>
> </threads>
Thanks, but can we put some string without dots there? IOW, an
example of a real-life "handle" attribute, like the rest of the
example does?
next prev parent reply other threads:[~2024-04-02 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 10:20 Tankut Baris Aktemur
2024-04-02 10:20 ` [PATCH 2/2] gdbserver, remote: introduce "id_str" in the "qXfer:threads:read" XML Tankut Baris Aktemur
2024-04-02 12:19 ` Eli Zaretskii
2024-04-03 14:57 ` [PATCH v2] " Tankut Baris Aktemur
2024-04-02 12:14 ` Eli Zaretskii [this message]
2024-04-03 14:49 ` [PATCH 1/2] doc: add the missing 'handle' attribute in xml Aktemur, Tankut Baris
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=86jzlg9d2k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tankut.baris.aktemur@intel.com \
/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).