From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19511 invoked by alias); 13 Mar 2012 23:15:00 -0000 Received: (qmail 19500 invoked by uid 22791); 13 Mar 2012 23:14:59 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_NONE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from elasmtp-scoter.atl.sa.earthlink.net (HELO elasmtp-scoter.atl.sa.earthlink.net) (209.86.89.67) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 13 Mar 2012 23:14:38 +0000 Received: from [68.96.200.16] (helo=macbook2.local) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1S7avN-0004LP-LB; Tue, 13 Mar 2012 19:14:37 -0400 Message-ID: <4F5FD4DD.1010603@earthlink.net> Date: Tue, 13 Mar 2012 23:15:00 -0000 From: Stan Shebs User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Joel Brobecker CC: gdb-patches@sourceware.org Subject: Re: [PATCH] dynamic printf References: <4F4DCDD5.2040807@earthlink.net> <20120229161337.GD3118@adacore.com> In-Reply-To: <20120229161337.GD3118@adacore.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: ae6f8838ff913eba0cc1426638a40ef67e972de0d01da9405db8b929822bbd1425c4db1f4af15f81350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c 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: 2012-03/txt/msg00457.txt.bz2 On 2/29/12 8:13 AM, Joel Brobecker wrote: >> This patch implements a "dynamic printf", which is basically a >> breakpoint with a printf;continue as its command list - but with >> additional features that make it more interesting. > Or like a tracepoint that does printf? Would it influence an operation > such as "next", for instance? > > There is a tracepoint similarity; one of the vague future-direction ideas is to somehow refactor tracing and breaking so one could shift back and forth freely, for instance to decide to collect some data at a breakpoint, without having to do the formalized trace experiment setup. I'm not sure what you mean by influencing "next"? Stan