From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17798 invoked by alias); 12 Feb 2011 00:33:04 -0000 Received: (qmail 17789 invoked by uid 22791); 12 Feb 2011 00:33:04 -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-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 12 Feb 2011 00:32:56 +0000 Received: from mailhost3.vmware.com (mailhost3.vmware.com [10.16.27.45]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id DE9EB6012; Fri, 11 Feb 2011 16:32:54 -0800 (PST) Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138]) by mailhost3.vmware.com (Postfix) with ESMTP id D22ECCD946; Fri, 11 Feb 2011 16:32:54 -0800 (PST) Message-ID: <4D55D536.3040804@vmware.com> Date: Sat, 12 Feb 2011 00:33:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.24 (X11/20101201) MIME-Version: 1.0 To: Pedro Alves CC: "gdb-patches@sourceware.org" Subject: Re: [rfc] 'thread tid' command References: <4D55B457.4090404@vmware.com> <201102112356.22969.pedro@codesourcery.com> In-Reply-To: <201102112356.22969.pedro@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-15; 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/msg00232.txt.bz2 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? > >> 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. I'm fine with a regex, but I don't particularly want to implement thread sets just now. Perhaps a future enhancement? ;-)