From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>
Subject: Re: [rfc] 'thread tid' command
Date: Fri, 11 Feb 2011 23:56:00 -0000 [thread overview]
Message-ID: <201102112356.22969.pedro@codesourcery.com> (raw)
In-Reply-To: <4D55B457.4090404@vmware.com>
On Friday 11 February 2011 22:12:39, Michael Snyder wrote:
> This is purposefully rough, 'cause I hope for discussion.
>
> This is a new command to help manage large thread lists.
> I started with the idea "I want to find out which thread
> has target id 12345", then extended it to also handle the
> new concept of thread names (which thread has name 'foo'),
> and extra info as well (which thread has extra info that
> includes the string "xyz").
>
> The syntax (I'm open to renaming etc.):
>
> thread tid [NAME | TARGET_ID | EXTRA_INFO]
Shouldn't this be under "info" or "show"?
> The output:
>
> Thread %d has name '%s' or
> Thread %d has target id '%s' or
> Thread %d has extra info '%s'
>
> The user can then use the given thread id as input to the
> thread command, info threads, etc.
>
> Comments?
I think that if you made this accept a regex, it'll
end up being much more useful. Particularly, to filter
the extra info fields. Another interesting filter
could be: threads stopped in "foo_regex" function,
or address.
But still, the user will still have to manually pick
the output of the previous command. I think it'd even
be better if the command had a switch that created a
thread group (itset or thread set, whatever) from the threads
that matched. Only problem is we don't have thread
sets support, yet.
--
Pedro Alves
next prev parent reply other threads:[~2011-02-11 23:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 22:12 Michael Snyder
2011-02-11 23:56 ` Pedro Alves [this message]
2011-02-12 0:33 ` Michael Snyder
2011-02-12 7:51 ` Eli Zaretskii
2011-02-12 22:52 ` Michael Snyder
2011-02-13 0:01 ` Michael Snyder
2011-02-12 7:44 ` Eli Zaretskii
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=201102112356.22969.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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