From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8446 invoked by alias); 18 Jan 2010 18:53:36 -0000 Received: (qmail 8433 invoked by uid 22791); 18 Jan 2010 18:53:34 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS 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; Mon, 18 Jan 2010 18:53:29 +0000 Received: (qmail 29262 invoked from network); 18 Jan 2010 18:53:27 -0000 Received: from unknown (HELO macbook-2.local) (stan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 18 Jan 2010 18:53:27 -0000 Message-ID: <4B54AE21.1070205@codesourcery.com> Date: Mon, 18 Jan 2010 18:53:00 -0000 From: Stan Shebs User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Joel Brobecker CC: Eli Zaretskii , stan@codesourcery.com, gdb@sourceware.org Subject: Re: [RFC] "actionpoints"? References: <4B5106CB.5060204@codesourcery.com> <20100118064348.GA1914@adacore.com> <83tyuj70yr.fsf@gnu.org> <20100118181819.GN5800@adacore.com> In-Reply-To: <20100118181819.GN5800@adacore.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2010-01/txt/msg00158.txt.bz2 Joel Brobecker wrote: >>> I don't think we should change all the user interface (eg: info >>> breakpoints") where it is already clear what the output is about. >>> >> ??? How is it clear? "info break" displays all ``actionpoints'' >> regardless of their kind, last time I tried. Am I missing something? >> > > Yeah, well, the command is misnamed. We can introduce aliases and > do a gradual transition, if we want. As a small quasi-data-point, in my tracepoint tinkering, I noticed that once breakpoints and tracepoints were merged, I drifted into the habit of doing "info b" even when I'm only wanting to see the list of tracepoints. That might just be because the list has tended to be short, only around five action/event/x/*points in all; I imagine that filtering by type gets more interesting at 10 and up, as happens with rbreak and the like. Stan