From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20616 invoked by alias); 19 Sep 2011 20:14:08 -0000 Received: (qmail 20603 invoked by uid 22791); 19 Sep 2011 20:14:07 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 19 Sep 2011 20:13:51 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 989C92BAEF0; Mon, 19 Sep 2011 16:13:50 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 0OQQ8uskNANa; Mon, 19 Sep 2011 16:13:50 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 697662BAEE8; Mon, 19 Sep 2011 16:13:50 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 8A95F145615; Mon, 19 Sep 2011 16:13:36 -0400 (EDT) Date: Tue, 20 Sep 2011 04:12:00 -0000 From: Joel Brobecker To: Vladimir Prus Cc: gdb-patches@sourceware.org Subject: Re: [RFA 1/3] [Ada] New GDB/MI command: -ada-tasks-info Message-ID: <20110919201336.GF17681@adacore.com> References: <1316205921-18702-1-git-send-email-brobecker@adacore.com> <1316205921-18702-2-git-send-email-brobecker@adacore.com> <201109192126.26235.vladimir@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201109192126.26235.vladimir@codesourcery.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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-09/txt/msg00368.txt.bz2 > I don't have any questions about the implementation, but I do wonder > whether reusing "info os xxx" mechanism might be better here, e.g.: > > info os ada-tasks I don't think it makes sense in this case. I could see system-wide queries, or os-specific commands to use that prefix. But I don't see how the list of Ada tasks would fit in the `info os' prefix. Ada tasks and threads are very similar, so I would treat them the same. -- Joel