From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6796 invoked by alias); 24 Mar 2007 00:09:42 -0000 Received: (qmail 6787 invoked by uid 22791); 24 Mar 2007 00:09:41 -0000 X-Spam-Check-By: sourceware.org Received: from hq.tensilica.com (HELO mailapp.tensilica.com) (65.205.227.29) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 24 Mar 2007 00:09:38 +0000 Received: from localhost ([127.0.0.1]) by mailapp.tensilica.com with esmtp (Exim 4.34) id 1HUtpA-0002s8-4s for gdb-patches@sources.redhat.com; Fri, 23 Mar 2007 16:09:36 -0800 Received: from mailapp.tensilica.com ([127.0.0.1]) by localhost (mailapp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09013-03 for ; Fri, 23 Mar 2007 16:09:36 -0800 (PST) Received: from heron.hq.tensilica.com ([192.168.11.123]) by mailapp.tensilica.com with esmtp (Exim 4.34) id 1HUtp9-0002s2-Qh for gdb-patches@sources.redhat.com; Fri, 23 Mar 2007 16:09:35 -0800 Received: from [192.168.11.123] (heron.hq.tensilica.com [192.168.11.123]) by heron.hq.tensilica.com (Postfix) with ESMTP id D18DBAC66E for ; Fri, 23 Mar 2007 17:09:35 -0700 (PDT) Message-ID: <46046C3F.5030702@tensilica.com> Date: Sat, 24 Mar 2007 00:09:00 -0000 From: Bob Wilson User-Agent: Thunderbird 1.5.0.10 (X11/20070306) MIME-Version: 1.0 To: gdb-patches@sources.redhat.com Subject: [PATCH] use texinfo variables in doc Content-Type: multipart/mixed; boundary="------------000503000706030601070004" 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-03/txt/msg00215.txt.bz2 This is a multi-part message in MIME format. --------------000503000706030601070004 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-length: 444 There were a few places where the texinfo variables GDBP, GDBN, and GCC were not used. OK? 2007-03-23 Bob Wilson * gdb.texinfo (Invoking GDB): Use @value{GDBP}. (Source Path, Character Sets, Macros, Define) (GDB/MI Result Records, GDB/MI Simple Examples) (GDB/MI Program Execution, GDB/MI File Commands) (Maintenance Commands, Packets, File-I/O Overview): Use @value{GDBN}. (Bug Reporting): Use @value{GCC}. --------------000503000706030601070004 Content-Type: text/plain; name="gdb-doc-vars.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="gdb-doc-vars.patch" Content-length: 5928 Index: gdb.texinfo =================================================================== RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v retrieving revision 1.389 diff -u -r1.389 gdb.texinfo --- gdb.texinfo 26 Feb 2007 20:10:17 -0000 1.389 +++ gdb.texinfo 24 Mar 2007 00:04:01 -0000 @@ -842,7 +842,7 @@ executable file to the inferior using @code{--args}. This option stops option processing. @smallexample -gdb --args gcc -O2 -c foo.c +@value{GDBP} --args gcc -O2 -c foo.c @end smallexample This will cause @code{@value{GDBP}} to debug @code{gcc}, and to set @code{gcc}'s command-line arguments (@pxref{Arguments}) to @samp{-O2 -c foo.c}. @@ -5136,7 +5136,7 @@ Using the previous example, suppose the @file{foo-1.0} tree has been moved from @file{/usr/src} to @file{/mnt/cross}, then you can tell -GDB to replace @file{/usr/src} in all source path names with +@value{GDBN} to replace @file{/usr/src} in all source path names with @file{/mnt/cross}. The first lookup will then be @file{/mnt/cross/foo-1.0/lib/foo.c} in place of the original location of @file{/usr/src/foo-1.0/lib/foo.c}. To define a source path @@ -5166,7 +5166,7 @@ the debugger behavior to look at the rewritten location instead. So, if for any reason a source file that is not relevant to your executable is located at the original location, a substitution rule is the only -method available to point GDB at the new location. +method available to point @value{GDBN} at the new location. @table @code @item directory @var{dirname} @dots{} @@ -7189,7 +7189,7 @@ @end table Note that these are all single-byte character sets. More work inside -GDB is needed to support multi-byte or variable-width character +@value{GDBN} is needed to support multi-byte or variable-width character encodings, like the UTF-8 and UCS-2 encodings of Unicode. Here is an example of @value{GDBN}'s character set support in action. @@ -7537,8 +7537,8 @@ @code{ADD} --- but does not expand the invocation of the macro @code{M}, which was introduced by @code{ADD}. -Once the program is running, GDB uses the macro definitions in force at -the source line of the current stack frame: +Once the program is running, @value{GDBN} uses the macro definitions in +force at the source line of the current stack frame: @smallexample (@value{GDBP}) break main @@ -16482,7 +16482,7 @@ @item show max-user-call-depth @itemx set max-user-call-depth The value of @code{max-user-call-depth} controls how many recursion -levels are allowed in user-defined commands before GDB suspects an +levels are allowed in user-defined commands before @value{GDBN} suspects an infinite recursion and aborts the command. @end table @@ -17818,7 +17818,7 @@ @item "^connected" @findex ^connected -GDB has connected to a remote target. +@value{GDBN} has connected to a remote target. @item "^error" "," @var{c-string} @findex ^error @@ -17827,7 +17827,7 @@ @item "^exit" @findex ^exit -GDB has terminated. +@value{GDBN} has terminated. @end table @@ -17956,9 +17956,9 @@ <- (gdb) @end smallexample -@subheading Quitting GDB +@subheading Quitting @value{GDBN} -Quitting GDB just prints the result class @samp{^exit}. +Quitting @value{GDBN} just prints the result class @samp{^exit}. @smallexample -> (gdb) @@ -18878,7 +18878,7 @@ @section @sc{gdb/mi} Program Execution These are the asynchronous commands which generate the out-of-band -record @samp{*stopped}. Currently GDB only really executes +record @samp{*stopped}. Currently @value{GDBN} only really executes asynchronously with remote targets and this interaction is mimicked in other cases. @@ -20909,8 +20909,8 @@ List the source files for the current executable. -It will always output the filename, but only when GDB can find the absolute -file name of a source file, will it output the fullname. +It will always output the filename, but only when @value{GDBN} can find +the absolute file name of a source file, will it output the fullname. @subsubheading @value{GDBN} Command @@ -22049,9 +22049,9 @@ @item What compiler (and its version) was used to compile the program you are debugging---e.g.@: ``@value{GCC}--2.8.1'', or ``HP92453-01 A.10.32.03 HP -C Compiler''. For @value{NGCC}, you can say @kbd{gcc --version} to get this -information; for other compilers, see the documentation for those -compilers. +C Compiler''. For @value{NGCC}, you can say @kbd{@value{GCC} --version} +to get this information; for other compilers, see the documentation for +those compilers. @item The command arguments you gave the compiler to compile your example and @@ -22848,7 +22848,7 @@ @item maint show-debug-regs Control whether to show variables that mirror the x86 hardware debug registers. Use @code{ON} to enable, @code{OFF} to disable. If -enabled, the debug registers values are shown when GDB inserts or +enabled, the debug registers values are shown when @value{GDBN} inserts or removes a hardware breakpoint or watchpoint, and when the inferior triggers a hardware-assisted breakpoint or watchpoint. @@ -23049,7 +23049,7 @@ separate its components. For example, a template like @samp{foo @var{bar} @var{baz}} describes a packet beginning with the three ASCII bytes @samp{foo}, followed by a @var{bar}, followed directly by a -@var{baz}. GDB does not transmit a space character between the +@var{baz}. @value{GDBN} does not transmit a space character between the @samp{foo} and the @var{bar}, or between the @var{bar} and the @var{baz}. @@ -24571,8 +24571,8 @@ (@value{GDBP}) continue <- target requests 'system call X' target is stopped, @value{GDBN} executes system call - -> GDB returns result - ... target continues, GDB returns to wait for the target + -> @value{GDBN} returns result + ... target continues, @value{GDBN} returns to wait for the target <- target hits breakpoint and sends a Txx packet @end smallexample --------------000503000706030601070004--