From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11214 invoked by alias); 12 Mar 2010 08:17:32 -0000 Received: (qmail 11203 invoked by uid 22791); 12 Mar 2010 08:17:32 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 12 Mar 2010 08:17:24 +0000 Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0KZ500K00TKMIO00@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Fri, 12 Mar 2010 10:17:21 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.70.214.230]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KZ500J6FTOWGF40@a-mtaout21.012.net.il>; Fri, 12 Mar 2010 10:17:21 +0200 (IST) Date: Fri, 12 Mar 2010 08:17:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH] Document tracepoint restrictions In-reply-to: <4B99A9A0.20500@codesourcery.com> To: Stan Shebs Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83ociu0x9l.fsf@gnu.org> References: <4B99A9A0.20500@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: 2010-03/txt/msg00438.txt.bz2 > Date: Thu, 11 Mar 2010 18:40:32 -0800 > From: Stan Shebs > > While the savvy GDB hacker can use sekrit GDB internals knowledge to > surmise what will and won't work with tracepoints, normal users can > benefit from it being spelled out more explicitly. This patch adds a > new section to the manual that explains some of the gotchas our new > generation of tracepoint users has experienced already. Thanks. > + @node Tracepoint Restrictions > + @subsection Tracepoint Restrictions > + > + There are a number of restrictions on the use of tracepoints. As always, it is generally a good idea to have a @cindex entry whose name is like the section name (in lower-case). > + state variables). Objective-C and Objective-C++ features are not > + supported. I'm not sure I understand the last sentence. How are Objective-C/C++ features related to tracepoints? Perhaps you should add some explanation. > + program -- particularly if a conditional branch is stepped. ^^^^ This should be 3 dashes in a row, and probably without spaces surrounding it. That way, it will look better in print. > + collect not only the pointer, but the memory pointed to. For example > + @code{*ptr@@50} can be used to collect the 50 element array pointed to > + by @code{ptr}. A comma is missing after "For example". > + tracepoint. Instead you may collect the registers and a few hundred ^ A comma is missing here. > + bytes from the stack pointer with something like @code{*$esp@@300} > + (adjust to use the name of the actual stack pointer register on your > + target architecture, and the amount of stack you wish to capture). Isn't it better to just use the generic $sp here? Or are you saying that it is not supported by tracepoints? > + The above is not intended as an exhaustive list of restrictions. As > + described above, tracepoint data gathering occurs on the target > + without interaction from GDB. Thus the full capabilities of GDB are > + not available during data gathering. This should probably be moved to before the list, and rephrased appropriately. Okay with these changes.