From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22925 invoked by alias); 12 Feb 2011 07:51:13 -0000 Received: (qmail 22917 invoked by uid 22791); 12 Feb 2011 07:51:12 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout23.012.net.il (HELO mtaout23.012.net.il) (80.179.55.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 12 Feb 2011 07:51:07 +0000 Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0LGH00800V1YCC00@a-mtaout23.012.net.il> for gdb-patches@sourceware.org; Sat, 12 Feb 2011 09:51:04 +0200 (IST) Received: from HOME-C4E4A596F7 ([84.229.171.5]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LGH0081DV535XC0@a-mtaout23.012.net.il>; Sat, 12 Feb 2011 09:51:04 +0200 (IST) Date: Sat, 12 Feb 2011 07:51:00 -0000 From: Eli Zaretskii Subject: Re: [rfc] 'thread tid' command In-reply-to: <4D55D536.3040804@vmware.com> To: Michael Snyder Cc: pedro@codesourcery.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83aai1r8qr.fsf@gnu.org> References: <4D55B457.4090404@vmware.com> <201102112356.22969.pedro@codesourcery.com> <4D55D536.3040804@vmware.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/msg00236.txt.bz2 > 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]