From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7006 invoked by alias); 11 Feb 2011 23:56:44 -0000 Received: (qmail 6997 invoked by uid 22791); 11 Feb 2011 23:56:43 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 11 Feb 2011 23:56:30 +0000 Received: (qmail 21477 invoked from network); 11 Feb 2011 23:56:28 -0000 Received: from unknown (HELO scottsdale.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 11 Feb 2011 23:56:28 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [rfc] 'thread tid' command Date: Fri, 11 Feb 2011 23:56:00 -0000 User-Agent: KMail/1.13.5 (Linux/2.6.35-25-generic; KDE/4.6.0; x86_64; ; ) Cc: Michael Snyder References: <4D55B457.4090404@vmware.com> In-Reply-To: <4D55B457.4090404@vmware.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201102112356.22969.pedro@codesourcery.com> 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/msg00229.txt.bz2 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