From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3506 invoked by alias); 18 Jan 2010 18:44:34 -0000 Received: (qmail 3496 invoked by uid 22791); 18 Jan 2010 18:44: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:44:29 +0000 Received: (qmail 23631 invoked from network); 18 Jan 2010 18:44:27 -0000 Received: from unknown (HELO macbook-2.local) (stan@127.0.0.2) by mail.codesourcery.com with ESMTPA; 18 Jan 2010 18:44:27 -0000 Message-ID: <4B54AC04.7090204@codesourcery.com> Date: Mon, 18 Jan 2010 18:44:00 -0000 From: Stan Shebs User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Joel Brobecker CC: Stan Shebs , gdb@sourceware.org Subject: Re: [RFC] "actionpoints"? References: <4B5106CB.5060204@codesourcery.com> <20100118064348.GA1914@adacore.com> In-Reply-To: <20100118064348.GA1914@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/msg00157.txt.bz2 Joel Brobecker wrote: >> One of the issues that has come up regularly in our tracepoint work >> is what GDB's messages to the user should say when they are >> referring to various combinations of tracepoints and breakpoints. >> > > I like the idea of having a term that means either breakpoint/watchpoint/ > tracepoint, etc. How about "eventpoint"? "actionpoint" sounds OK to me too. > "eventpoint" is a good candidate. Googling shows it in VxWorks and the old VAX/VMS debugger - and a couple dozen appearances in GDB sources(!); most likely inherited from HP code, which was partly written by ex-DEC people... To me "eventpoint" has a slight downside in that it is used in several OS debugging/monitoring tools, tied to various notions of system-level "event", so the manual would have to emphasize that our notion of eventpoint is not OS-related in any way. But that doesn't seem too difficult to explain. Stan