From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12661 invoked by alias); 12 Feb 2011 22:52:01 -0000 Received: (qmail 12649 invoked by uid 22791); 12 Feb 2011 22:52:00 -0000 X-SWARE-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 12 Feb 2011 22:51:55 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 9E99B4E000; Sat, 12 Feb 2011 14:51:51 -0800 (PST) Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138]) by mailhost4.vmware.com (Postfix) with ESMTP id 93184C9DE9; Sat, 12 Feb 2011 14:51:51 -0800 (PST) Message-ID: <4D570F07.2090802@vmware.com> Date: Sat, 12 Feb 2011 22:52:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.24 (X11/20101201) MIME-Version: 1.0 To: Eli Zaretskii CC: "pedro@codesourcery.com" , "gdb-patches@sourceware.org" Subject: Re: [rfc] 'thread tid' command References: <4D55B457.4090404@vmware.com> <201102112356.22969.pedro@codesourcery.com> <4D55D536.3040804@vmware.com> <83aai1r8qr.fsf@gnu.org> In-Reply-To: <83aai1r8qr.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-02/txt/msg00241.txt.bz2 Eli Zaretskii wrote: >> Date: Fri, 11 Feb 2011 16:32:54 -0800 >> From: Michael Snyder >> CC: "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"?