From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25536 invoked by alias); 8 Nov 2011 01:14:29 -0000 Received: (qmail 25524 invoked by uid 22791); 8 Nov 2011 01:14:27 -0000 X-SWARE-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-ey0-f169.google.com (HELO mail-ey0-f169.google.com) (209.85.215.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 08 Nov 2011 01:14:14 +0000 Received: by eye4 with SMTP id 4so4515128eye.0 for ; Mon, 07 Nov 2011 17:14:13 -0800 (PST) MIME-Version: 1.0 Received: by 10.14.8.147 with SMTP id 19mr2357440eer.128.1320714853207; Mon, 07 Nov 2011 17:14:13 -0800 (PST) Received: by 10.14.48.67 with HTTP; Mon, 7 Nov 2011 17:14:13 -0800 (PST) In-Reply-To: <20111107173729.GD335@adacore.com> References: <4EB088E7.8040107@earthlink.net> <20111107173729.GD335@adacore.com> Date: Tue, 08 Nov 2011 01:14:00 -0000 Message-ID: Subject: Re: Toward multicore GDB - Set theory From: Daniel Jacobowitz To: Joel Brobecker Cc: Tom Tromey , Stan Shebs , gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-11/txt/msg00055.txt.bz2 On Mon, Nov 7, 2011 at 12:37 PM, Joel Brobecker wro= te: > > > I think in the past we talked about square brackets and prefix. > > How about we consider that as a straw proposal? > > > > (gdb) [0-13] print x > > I like this option best. > Me, too.=A0 I expect this to be a power user feature and plumbing for IDEs; you won't very often want to specify this stuff by hand. But if we make it easy to name groups of threads, then the abbreviations may be more commonly used. Ideally I'd like to be able to hook this with Python, so that a new thread can be categorized in some application-specific way. For example, it's common in the program I work on to have pools of threads for a specific purpose. You don't always want to treat the request processing threads and the RPC threads the same way, but you don't care which request processing thread hits your breakpoint - and they can be created and destroyed dynamically. -- Thanks, Daniel