This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc] 'thread tid' command
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Cc: Michael Snyder <msnyder at vmware dot com>
- Date: Fri, 11 Feb 2011 23:56:22 +0000
- Subject: Re: [rfc] 'thread tid' command
- References: <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