From: "Aktemur, Tankut Baris via Gdb-patches" <gdb-patches@sourceware.org>
To: Eli Zaretskii <eliz@gnu.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 3/3] gdb: add a '-stopped' option to "info threads"
Date: Wed, 5 Apr 2023 10:19:26 +0000 [thread overview]
Message-ID: <DM4PR11MB73034D693AE35D7B9BA24A5BC4909@DM4PR11MB7303.namprd11.prod.outlook.com> (raw)
In-Reply-To: <83ileasl6h.fsf@gnu.org>
On Wednesday, April 5, 2023 12:01 PM, Eli Zaretskii wrote:
> > Date: Wed, 5 Apr 2023 11:20:02 +0200
> > From: Tankut Baris Aktemur via Gdb-patches <gdb-patches@sourceware.org>
> >
> > gdb/NEWS | 7 ++
> > gdb/doc/gdb.texinfo | 6 +-
> > gdb/testsuite/gdb.base/options.exp | 11 ++-
> > .../gdb.threads/info-threads-stopped.c | 78 +++++++++++++++++++
> > .../gdb.threads/info-threads-stopped.exp | 75 ++++++++++++++++++
> > gdb/thread.c | 17 +++-
> > 6 files changed, 190 insertions(+), 4 deletions(-)
> > create mode 100644 gdb/testsuite/gdb.threads/info-threads-stopped.c
> > create mode 100644 gdb/testsuite/gdb.threads/info-threads-stopped.exp
>
> Thanks, the documentation parts are OK.
>
> But I have a question about the new behavior:
>
> > (gdb) info threads -stopped 3
> > No stopped threads match '3'.
>
> Is it really useful to show nothing and emit an error message if
> explicit thread IDs were specified by the user? Wouldn't it be better
> to ignore the -stopped switch in that case?
>
> Reviewed-By: Eli Zaretskii <eliz@gnu.org>
The user may have given a thread id range or a wildcard, like
"info threads -stopped 1-999" or "info threads -stopped 2.*".
Ignoring the flag for these cases can output a very long list.
I'm fine if we make the single thread id a special case. But then
the question is, where do we draw the line? If the user gave just a
few thread ids, do we still ignore the flag? What is the limit to
the acceptable list length? Because of these questions, consistently
applying the flag made more sense to me.
Regards
-Baris
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2023-04-05 10:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 9:19 [PATCH 0/3] Option to show stopped threads only Tankut Baris Aktemur via Gdb-patches
2023-04-05 9:20 ` [PATCH 1/3] gdb: pass info_threads_opts to print_thread_info_1 Tankut Baris Aktemur via Gdb-patches
2023-04-05 9:20 ` [PATCH 2/3] gdb, doc: add the missing '-gid' option to 'info threads' Tankut Baris Aktemur via Gdb-patches
2023-04-05 9:56 ` Eli Zaretskii via Gdb-patches
2023-04-05 10:12 ` Aktemur, Tankut Baris via Gdb-patches
2023-04-05 9:20 ` [PATCH 3/3] gdb: add a '-stopped' option to "info threads" Tankut Baris Aktemur via Gdb-patches
2023-04-05 10:00 ` Eli Zaretskii via Gdb-patches
2023-04-05 10:19 ` Aktemur, Tankut Baris via Gdb-patches [this message]
2023-04-05 10:50 ` Eli Zaretskii via Gdb-patches
2023-04-05 11:31 ` Aktemur, Tankut Baris via Gdb-patches
2023-04-05 11:56 ` Eli Zaretskii via Gdb-patches
2025-04-24 14:50 ` Pedro Alves
2025-03-18 18:04 ` [PATCH v2 0/2] Option to show stopped threads only Tankut Baris Aktemur
2025-03-18 18:05 ` [PATCH v2 1/2] gdb: pass info_threads_opts to print_thread_info_1 Tankut Baris Aktemur
2025-03-18 18:05 ` [PATCH v2 2/2] gdb: add a '-stopped' option to "info threads" Tankut Baris Aktemur
2025-03-28 16:38 ` [PATCH v2 0/2] Option to show stopped threads only Guinevere Larsen
2025-04-04 13:39 ` Aktemur, Tankut Baris
2025-04-04 13:36 ` [PATCH v3 " Tankut Baris Aktemur
2025-04-04 13:36 ` [PATCH v3 1/2] gdb: pass info_threads_opts to print_thread_info_1 Tankut Baris Aktemur
2025-04-24 18:09 ` Pedro Alves
2025-04-04 13:36 ` [PATCH v3 2/2] gdb: add a '-stopped' option to "info threads" Tankut Baris Aktemur
2025-04-24 19:23 ` Pedro Alves
2025-05-05 16:17 ` Aktemur, Tankut Baris
2025-04-23 8:00 ` [PATCH v3 0/2] Option to show stopped threads only Aktemur, Tankut Baris
2025-04-24 17:53 ` Pedro Alves
2025-05-05 16:19 ` [PATCH v4 0/3] Option to show stopped/running " Tankut Baris Aktemur
2025-05-05 16:19 ` [PATCH v4 1/3] gdb: pass info_threads_opts to print_thread_info_1 Tankut Baris Aktemur
2025-05-05 16:19 ` [PATCH v4 2/3] gdb: update "info threads" output when no threads match the arguments Tankut Baris Aktemur
2025-05-05 17:19 ` Eli Zaretskii
2025-05-05 16:19 ` [PATCH v4 3/3] gdb: add '-stopped' and '-running' options to "info threads" Tankut Baris Aktemur
2025-05-05 17:21 ` Eli Zaretskii
2025-05-09 20:54 ` [PATCH v4 0/3] Option to show stopped/running threads only Pedro Alves
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=DM4PR11MB73034D693AE35D7B9BA24A5BC4909@DM4PR11MB7303.namprd11.prod.outlook.com \
--to=gdb-patches@sourceware.org \
--cc=eliz@gnu.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