From: Michael Snyder <msnyder@vmware.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "pedro@codesourcery.com" <pedro@codesourcery.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [rfc] 'thread tid' command
Date: Sat, 12 Feb 2011 22:52:00 -0000 [thread overview]
Message-ID: <4D570F07.2090802@vmware.com> (raw)
In-Reply-To: <83aai1r8qr.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Fri, 11 Feb 2011 16:32:54 -0800
>> From: Michael Snyder <msnyder@vmware.com>
>> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>>
>> Pedro Alves wrote:
>>> 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"?
>> Suits me, but
>> 1) I'd prefer it wasn't "show", because there is no "set".
>> 2) Info what? tid? thread-id?
>
> thread show [NAME | TARGET_ID | EXTRA_INFO]
> thread info [NAME | TARGET_ID | EXTRA_INFO]
How about "thread find"?
next prev parent reply other threads:[~2011-02-12 22:52 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
2011-02-12 0:33 ` Michael Snyder
2011-02-12 7:51 ` Eli Zaretskii
2011-02-12 22:52 ` Michael Snyder [this message]
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=4D570F07.2090802@vmware.com \
--to=msnyder@vmware.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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