From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12968 invoked by alias); 11 Jul 2007 22:56:13 -0000 Received: (qmail 12955 invoked by uid 22791); 11 Jul 2007 22:56:13 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 11 Jul 2007 22:56:10 +0000 Received: from kahikatea.snap.net.nz (214.63.255.123.dynamic.snap.net.nz [123.255.63.214]) by viper.snap.net.nz (Postfix) with ESMTP id 84A3B3DA0C7; Thu, 12 Jul 2007 10:56:06 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id ECD978FBF6; Thu, 12 Jul 2007 10:56:04 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18069.24580.179474.972686@kahikatea.snap.net.nz> Date: Wed, 11 Jul 2007 22:56:00 -0000 To: Jim Blandy Cc: Daniel Jacobowitz , gdb-patches@sourceware.org Subject: Re: $_ and info breakpoint [PATCH: doco] In-Reply-To: References: <18064.7905.924535.720690@kahikatea.snap.net.nz> <20070709115647.GC3095@caradoc.them.org> <18066.53564.134378.88590@kahikatea.snap.net.nz> X-Mailer: VM 7.19 under Emacs 22.1.50.14 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: 2007-07/txt/msg00180.txt.bz2 > > This shouldn't affect existing use and we can put a caveat in the > > documentaion in the manual: > > > > The convenience variable `$_' and the default > > examining-address for the `x' command are set to the address of > > the last breakpoint listed unless the command is prefixed with > > 'server ' (see Command History). > > I have no warlord M-DEL patch, but I just wanted to point out that > 'server' should be documented more clearly than it is. How about this? (adapted fron the "Server Prefix" node in annotate.texinfo) -- Nick http://www.inet.net.nz/~nickrob 2007-07-12 Nick Roberts * gdb.texinfo (Server Prefix): New node. Adapt from existing node in annotate.texinfo. (Command History): Link to new node. *** gdb.texinfo 04 Jul 2007 17:37:49 +1200 1.420 --- gdb.texinfo 12 Jul 2007 10:50:38 +1200 *************** package, to provide the history facility *** 15436,15442 **** Interactively}, for the detailed description of the History library. To issue a command to @value{GDBN} without affecting certain aspects of ! the state which is seen by users, prefix it with @samp{server }. This means that this command will not affect the command history, nor will it affect @value{GDBN}'s notion of which command to repeat if @key{RET} is pressed on a line by itself. --- 15436,15443 ---- Interactively}, for the detailed description of the History library. To issue a command to @value{GDBN} without affecting certain aspects of ! the state which is seen by users, prefix it with @samp{server } ! (@pxref{Server Prefix}). This means that this command will not affect the command history, nor will it affect @value{GDBN}'s notion of which command to repeat if @key{RET} is pressed on a line by itself. *************** This is Edition @value{EDITION}, @value{ *** 21241,21246 **** --- 21242,21248 ---- @menu * Annotations Overview:: What annotations are; the general syntax. + * Server Prefix:: Issuing a command without affecting user state. * Prompting:: Annotations marking @value{GDBN}'s need for input. * Errors:: Annotations for error messages. * Invalidation:: Some annotations describe things now invalid. *************** Here @samp{quit} is input to @value{GDBN *** 21319,21324 **** --- 21321,21340 ---- denotes a @samp{control-z} character) are annotations; the rest is output from @value{GDBN}. + @node Server Prefix + @section The Server Prefix + @cindex server prefix for annotations + + If you prefix a command with @samp{server } then it will not affect + the command history, nor will it affect @value{GDBN}'s notion of which + command to repeat if @key{RET} is pressed on a line by itself. This + means that commands can be run behind a user's back by a front-end in + a transparent manner. + + The server prefix does not affect the recording of values into the value + history; to print a value without recording it into the value history, + use the @code{output} command instead of the @code{print} command. + @node Prompting @section Annotation for @value{GDBN} Input