From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29415 invoked by alias); 20 Oct 2011 20:18:44 -0000 Received: (qmail 29406 invoked by uid 22791); 20 Oct 2011 20:18:43 -0000 X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,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; Thu, 20 Oct 2011 20:18:28 +0000 Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0LTD00M00S3CUP00@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Thu, 20 Oct 2011 22:17:40 +0200 (IST) Received: from HOME-C4E4A596F7 ([77.124.212.197]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LTD00M2LSDFUB20@a-mtaout21.012.net.il>; Thu, 20 Oct 2011 22:17:40 +0200 (IST) Date: Thu, 20 Oct 2011 20:40:00 -0000 From: Eli Zaretskii Subject: Re: Status of 'blacklist' patch? In-reply-to: To: Justin Lebar Cc: dje@google.com, stanshebs@earthlink.net, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83ipnjs9i1.fsf@gnu.org> References: <4E8DCE67.80507@earthlink.net> <4E92E639.7000402@earthlink.net> 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-10/txt/msg00577.txt.bz2 > From: Justin Lebar > Date: Sun, 16 Oct 2011 12:40:39 -0400 > Cc: Stan Shebs , gdb-patches@sourceware.org > > Added a NEWS entry in this patch. Thanks. > +* GDB now allows you to skip over uninteresting functions and files when ^^^^^^^^^ I think either "step over" or just "skip". > +@node Skipping Over Functions and Files > +@subsection Skipping Over Functions and Files > +@cindex skip This @cindex entry would be better if it just said what the subsection name says: @cindex skipping over functions and files > +The program you are debugging may contain some functions which are > +uninteresting to debug. The @code{skip} comand lets you tell @value{GDBN} to > +skip over a file or function when stepping. Again, I think this is better: ... to skip a function or all functions in a file ... > +A more flexible solution is to execute @code{skip boring}. This instructs ^^^^^^^^^^^^^^^^^^ @kbd{skip boring}, since this is something the user types on the keyboard. > +You can also instruct @value{GDBN} to skip all functions in a file, with, for > +example, @code{skip file boring.c}. What happens if I have a function called "file" in the same program? IOW, to what degree is "file" a reserved keyword here? > +@table @code > +@kindex skip > +@kindex skip function No need for two @kindex entries here, the second one is enough. > +stepping. (@pxref{Specify Location}) Just @xref, and no parentheses, like so: @xref{Specify Location}. > +@item Type > +@samp{function} or @samp{file} The text below the @item line should be at least one complete sentence. > +being skipped. If you've set a function skip on a function which has not yet > +been loaded, this field will contain @samp{}. Once a shared library > +which has the function is loaded, @code{info break} will show the function's ^^^^^^^^^^ I guess you meant "info skip", right? Okay with those changes. Thanks.