From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv2] gdb: new $_inferior_thread_count convenience variable
Date: Thu, 03 Nov 2022 16:48:51 +0200 [thread overview]
Message-ID: <83mt986qlo.fsf@gnu.org> (raw)
In-Reply-To: <20221103144239.98993-1-aburgess@redhat.com> (message from Andrew Burgess via Gdb-patches on Thu, 3 Nov 2022 14:42:39 +0000)
> Date: Thu, 3 Nov 2022 14:42:39 +0000
> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
>
> gdb/NEWS | 3 +++
> gdb/doc/gdb.texinfo | 14 ++++++++++++--
> gdb/testsuite/gdb.base/default.exp | 1 +
> gdb/testsuite/gdb.multi/tids.exp | 20 ++++++++++++++++++++
> gdb/thread.c | 26 ++++++++++++++++++++++++++
> gdbsupport/iterator-range.h | 4 ++++
> 6 files changed, 66 insertions(+), 2 deletions(-)
OK for the documentation parts, thanks.
next prev parent reply other threads:[~2022-11-03 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 14:34 [PATCH] gdb: new $_inferior_threads " Andrew Burgess
2022-11-02 14:56 ` Simon Marchi
2022-11-02 15:07 ` Luis Machado
2022-11-03 14:42 ` [PATCHv2] gdb: new $_inferior_thread_count " Andrew Burgess
2022-11-03 14:48 ` Eli Zaretskii [this message]
2022-11-03 15:03 ` Luis Machado
2022-11-17 14:51 ` Andrew Burgess
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=83mt986qlo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@redhat.com \
--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).