From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32430 invoked by alias); 9 May 2011 19:35:28 -0000 Received: (qmail 32219 invoked by uid 22791); 9 May 2011 19:35:27 -0000 X-SWARE-Spam-Status: No, hits=-0.3 required=5.0 tests=AWL,BAYES_20,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 09 May 2011 19:35:13 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LKY006000WW4B00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Mon, 09 May 2011 22:35:11 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.234.175]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LKY0045D12EKGK0@a-mtaout20.012.net.il>; Mon, 09 May 2011 22:35:11 +0300 (IDT) Date: Mon, 09 May 2011 19:35:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH] Support for enabling/disabling tracepoints while a trace experiment is running In-reply-to: <4DC840FE.6050408@codesourcery.com> To: Kwok Cheung Yeung Cc: pedro@codesourcery.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <837h9zis5u.fsf@gnu.org> References: <4DC2DDEF.10600@codesourcery.com> <83hb99m14x.fsf@gnu.org> <4DC32F21.9090400@codesourcery.com> <8339ksm85f.fsf@gnu.org> <4DC840FE.6050408@codesourcery.com> 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: 2011-05/txt/msg00228.txt.bz2 > Date: Mon, 09 May 2011 20:31:10 +0100 > From: Kwok Cheung Yeung > CC: gdb-patches@sourceware.org > > On 06/05/2011 11:32, Eli Zaretskii wrote: > > Btw, what if the target does not support this new feature? Do we > > still disallow to start a trace experiment with no enabled > > tracepoints? I think we should. > > > > I've now added 'EnableDisableTracepoints' to the list of features returned by > the qSupported packet from a patched gdbserver. GDB now checks whether this is > supported before trying to enable/disable a tracepoint on the target. If it is > not, then it silently reverts to the original behaviour. Thanks. This version of the docs is fine with me.