RFC: GDB as a loader 1/3: silent batch mode

RFC: GDB as a loader 1/3: silent batch mode

[Andrew STUBBS]

[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]

Hi all,

It is my experience that GDB is often used, by means of the --batch and
--command options, as a mechanism for downloading and running programs
on remote targets (development boards and the like). This may be using a
sledgehammer to crack a nut, but given that a debugger is always
required in these cases and that creating an additional specific loader
requires effort, it is not surprising that it is used for this purpose.

I have therefore created a number of features to make this process a
little more comfortable. I have split them into separate posts so that
they may be discussed separately.

All have been regression tested for both i686-pc-linux-gnu and sh-elf an
have produced no new failures. I have not attempted to produce any new
test cases. Probably there should be some, but where and how?

Silent Batch Mode

The attached patch implements a new option --batch-silent. This does
much the same a --batch, except that it also disables gdb_stdout. This
means that all GDB outputs, other than errors, are hidden.

The advantage of this is that I no longer have to create dodgy scripts
to filter out all the various GDB messages from my program output
(Loading section ..., Process exited successfully, etc.).

Obviously this is not particularly useful with targets such as the GDB
simulator that give their output through the GDB print mechanisms.
However, all targets which print via regular stdout (as our custom
target interface here at ST does) work fine. Perhaps somebody could
suggest a solution for those targets with which it does not work.

This patch does not affect the behaviour of stderr or gdb_stderr - an
error is still an error.

Thanks

Andrew Stubbs




[-- Attachment #2: batch-silent.patch --]
[-- Type: text/plain, Size: 2483 bytes --]

2005-10-18  Andrew Stubbs  <andrew.stubbs@st.com>

        * event-top.c (gdb_setup_readline): Don't set gdb_stdout when
        --batch-silent option was given.
        * main.c (batch_silent): New variable.
        (captured_main): Add new option --batch-silent.
        (print_gdb_help): Likewise.


Index: src/gdb/event-top.c
===================================================================
--- src.orig/gdb/event-top.c	2005-03-16 17:05:31.000000000 +0000
+++ src/gdb/event-top.c	2005-10-17 17:38:27.000000000 +0100
@@ -1110,8 +1110,10 @@ gdb_setup_readline (void)
      that the sync setup is ALL done in gdb_init, and we would only
      mess it up here.  The sync stuff should really go away over
      time.  */
+  extern batch_silent;
 
-  gdb_stdout = stdio_fileopen (stdout);
+  if (!batch_silent)
+    gdb_stdout = stdio_fileopen (stdout);
   gdb_stderr = stdio_fileopen (stderr);
   gdb_stdlog = gdb_stderr;  /* for moment */
   gdb_stdtarg = gdb_stderr; /* for moment */
Index: src/gdb/main.c
===================================================================
--- src.orig/gdb/main.c	2005-10-17 15:29:40.000000000 +0100
+++ src/gdb/main.c	2005-10-17 17:44:35.000000000 +0100
@@ -73,6 +73,9 @@ struct ui_file *gdb_stdtargin;
 struct ui_file *gdb_stdtarg;
 struct ui_file *gdb_stdtargerr;
 
+/* Support for the --batch-silent option.  */
+int batch_silent = 0;
+
 /* Whether to enable writing into executable and core files */
 extern int write_files;
 
@@ -254,6 +257,7 @@ captured_main (void *data)
       {"silent", no_argument, &quiet, 1},
       {"nx", no_argument, &inhibit_gdbinit, 1},
       {"n", no_argument, &inhibit_gdbinit, 1},
+      {"batch-silent", no_argument, 0, 'B'},
       {"batch", no_argument, &batch, 1},
       {"epoch", no_argument, &epoch_interface, 1},
 
@@ -384,6 +388,10 @@ captured_main (void *data)
 					     cmdsize * sizeof (*cmdarg));
 	      }
 	    break;
+	  case 'B':
+	    batch = batch_silent = 1;
+	    gdb_stdout = ui_file_new();
+	    break;
 #ifdef GDBTK
 	  case 'z':
 	    {
@@ -834,6 +842,7 @@ Options:\n\n\
   fputs_unfiltered (_("\
   -b BAUDRATE        Set serial port baud rate used for remote debugging.\n\
   --batch            Exit after processing options.\n\
+  --batch-silent     As for --batch, but suppress all gdb stdout output.\n\
   --cd=DIR           Change current directory to DIR.\n\
   --command=FILE     Execute GDB commands from FILE.\n\
   --core=COREFILE    Analyze the core dump COREFILE.\n\

Re: RFC: GDB as a loader 1/3: silent batch mode

[Eli Zaretskii]

> Date: Tue, 18 Oct 2005 12:26:55 +0100
> From: Andrew STUBBS <andrew.stubbs@st.com>
> 
> The attached patch implements a new option --batch-silent. This does
> much the same a --batch, except that it also disables gdb_stdout. This
> means that all GDB outputs, other than errors, are hidden.

Thanks.

If this patch is accepted, please also send additions to the GDB
manual that document the new command-line option.

Re: RFC: GDB as a loader 1/3: silent batch mode

[Andrew STUBBS]

Eli Zaretskii wrote:
>>Date: Tue, 18 Oct 2005 12:26:55 +0100
>>From: Andrew STUBBS <andrew.stubbs@st.com>
>>
>>The attached patch implements a new option --batch-silent. This does
>>much the same a --batch, except that it also disables gdb_stdout. This
>>means that all GDB outputs, other than errors, are hidden.
> 
> 
> Thanks.
> 
> If this patch is accepted, please also send additions to the GDB
> manual that document the new command-line option.
> 

OK, no problem. Test cases too if those are required.

I don't appear to be getting much feedback on these things. Is there 
anybody in particular I could point them at? There's nobody stands out 
in the MAINTAINERS file for these things.

I would like to get these ideas incorporated, but right now I'm feeling 
a little ignored. Maybe I'm just too used to instant gratification.

Thanks

Andrew Stubbs

Re: RFC: GDB as a loader 1/3: silent batch mode

[Eli Zaretskii]

> Date: Fri, 21 Oct 2005 15:24:44 +0100
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: gdb@sources.redhat.com
> 
> I don't appear to be getting much feedback on these things. Is there 
> anybody in particular I could point them at? There's nobody stands out 
> in the MAINTAINERS file for these things.

Any global maintainer can approve this, I think.  I suggest to wait
for a week, and if no one responds, see it as approved by me.

> I would like to get these ideas incorporated, but right now I'm feeling 
> a little ignored. Maybe I'm just too used to instant gratification.

People travel, get away of their mail, and otherwise engage in the
rest of their lives.  (I just returned from a 2-week travel during
which I didn't read my mail at all.)  Please be a little more patient.

Re: RFC: GDB as a loader 1/3: silent batch mode

[Andrew STUBBS]

Eli Zaretskii wrote:
> Any global maintainer can approve this, I think.  I suggest to wait
> for a week, and if no one responds, see it as approved by me.

Thanks. Do you mean a week from when it was posted or a week from now?

In any case, it's not like I have write access. I'll have to beg to get 
somebody to apply all my patches.

> People travel, get away of their mail, and otherwise engage in the
> rest of their lives.  (I just returned from a 2-week travel during
> which I didn't read my mail at all.)  Please be a little more patient.

Yeah, but the list of maintainers is quite long. We can but hope.

Andrew

Re: RFC: GDB as a loader 1/3: silent batch mode

[Daniel Jacobowitz]

On Fri, Oct 21, 2005 at 04:40:58PM +0100, Andrew STUBBS wrote:
> Eli Zaretskii wrote:
> >Any global maintainer can approve this, I think.  I suggest to wait
> >for a week, and if no one responds, see it as approved by me.
> 
> Thanks. Do you mean a week from when it was posted or a week from now?
> 
> In any case, it's not like I have write access. I'll have to beg to get 
> somebody to apply all my patches.
> 
> >People travel, get away of their mail, and otherwise engage in the
> >rest of their lives.  (I just returned from a 2-week travel during
> >which I didn't read my mail at all.)  Please be a little more patient.
> 
> Yeah, but the list of maintainers is quite long. We can but hope.

But most of them are not currently active, Eli was on vacation, and I
currently am.  I go over every posted patch and try to respond to
everything unreviewed, but I can only manage that every week or two.

As Eli said, please wait a little while.  I'll look at it when I
return.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: RFC: GDB as a loader 1/3: silent batch mode

[Andrew STUBBS]

Daniel Jacobowitz wrote:
> But most of them are not currently active, Eli was on vacation, and I
> currently am.  I go over every posted patch and try to respond to
> everything unreviewed, but I can only manage that every week or two.
> 
> As Eli said, please wait a little while.  I'll look at it when I
> return.

Thanks. I couldn't tell you were on holiday. Please don't read this till 
you get back :)

Andrew

Re: RFC: GDB as a loader 1/3: silent batch mode

[Eli Zaretskii]

> Date: Fri, 21 Oct 2005 16:40:58 +0100
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: gdb@sources.redhat.com
> 
> Eli Zaretskii wrote:
> > Any global maintainer can approve this, I think.  I suggest to wait
> > for a week, and if no one responds, see it as approved by me.
> 
> Thanks. Do you mean a week from when it was posted or a week from now?

A week from now.

Re: RFC: GDB as a loader 1/3: silent batch mode

[Andrew STUBBS]

[-- Attachment #1: Type: text/plain, Size: 501 bytes --]

Eli Zaretskii wrote:
>>Date: Tue, 18 Oct 2005 12:26:55 +0100
>>From: Andrew STUBBS <andrew.stubbs@st.com>
>>
>>The attached patch implements a new option --batch-silent. This does
>>much the same a --batch, except that it also disables gdb_stdout. This
>>means that all GDB outputs, other than errors, are hidden.
> 
> 
> Thanks.
> 
> If this patch is accepted, please also send additions to the GDB
> manual that document the new command-line option.
> 

Documentation patch attached.

Andrew Stubbs

[-- Attachment #2: batch-silent-docs.patch --]
[-- Type: text/plain, Size: 1047 bytes --]

2005-10-27  Andrew Stubbs  <andrew.stubbs@st.com>

	* gdb.texinfo (Choosing modes): Add --batch-silent.

Index: src/gdb/doc/gdb.texinfo
===================================================================
--- src.orig/gdb/doc/gdb.texinfo	2005-10-03 23:26:54.000000000 +0100
+++ src/gdb/doc/gdb.texinfo	2005-10-27 18:33:24.000000000 +0100
@@ -994,6 +994,18 @@ Program exited normally.
 @value{GDBN} control terminates) is not issued when running in batch
 mode.
 
+@item -batch-silent
+@cindex @code{--batch-silent}
+Run in batch mode exactly like @samp{-batch}, but totally silently. All GDB
+output to @code{stdout} is prevented (@code{stderr} is unaffected). This is
+much quieter than @samp{-silent} and would be useless for an interactive
+session.
+
+This is particularly useful when using targets that give @samp{Loading section} messages, for example.
+
+Note that targets that give their output via GDB, as opposed to writing
+directly to @code{stdout}, will also be made silent.
+
 @item -nowindows
 @itemx -nw
 @cindex @code{--nowindows}

Re: RFC: GDB as a loader 1/3: silent batch mode

[Eli Zaretskii]

> Date: Thu, 27 Oct 2005 18:55:00 +0100
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: gdb@sources.redhat.com
> 
> > If this patch is accepted, please also send additions to the GDB
> > manual that document the new command-line option.
> 
> Documentation patch attached.

Thanks.  This is approved, provided that you fix the minor problems
mentioned below.

> +Run in batch mode exactly like @samp{-batch}, but totally silently. All GDB
                                                                     ^^
Please make sure there are 2 spaces after a period that ends each
sentence.

> +Note that targets that give their output via GDB, as opposed to writing
                                                ^^^
Please use "@value{GDBN}" instead of a literal "GDB".

Re: RFC: GDB as a loader 1/3: silent batch mode

[Andrew STUBBS]

[-- Attachment #1: Type: text/plain, Size: 700 bytes --]

Eli Zaretskii wrote:
> Thanks.  This is approved, provided that you fix the minor problems
> mentioned below.

OK, updated patch attached.

Out of interest, why does 'GDB' have to be '@value{GDBN}'? What does 
that do?

I can create the info file fine, but the PDF has errors. The only thing 
I can see wrong with the produced file is that the index is missing. Is 
this a known problem or am I using the wrong version of something? I 
have Texinfo 4.5.

Still nobody has given an opinion on any of the three patches I sent 
adding new options. What do you want to do with them? Do we know if 
Daniel is back from holiday yet?

I'll do the docs for the other two options soon.

Thanks

Andrew Stubbs

[-- Attachment #2: batch-silent-docs.patch --]
[-- Type: text/plain, Size: 1066 bytes --]

2005-10-28  Andrew Stubbs  <andrew.stubbs@st.com>

	* gdb.texinfo (Choosing modes): Add --batch-silent.

Index: src/gdb/doc/gdb.texinfo
===================================================================
--- src.orig/gdb/doc/gdb.texinfo	2005-10-27 18:49:39.000000000 +0100
+++ src/gdb/doc/gdb.texinfo	2005-10-28 10:37:07.000000000 +0100
@@ -994,6 +994,18 @@ Program exited normally.
 @value{GDBN} control terminates) is not issued when running in batch
 mode.
 
+@item -batch-silent
+@cindex @code{--batch-silent}
+Run in batch mode exactly like @samp{-batch}, but totally silently. All
+@value{GDBN} output to @code{stdout} is prevented (@code{stderr} is
+unaffected).  This is much quieter than @samp{-silent} and would be useless
+for an interactive session.
+
+This is particularly useful when using targets that give @samp{Loading section} messages, for example.
+
+Note that targets that give their output via @value{GDBN}, as opposed to
+writing directly to @code{stdout}, will also be made silent.
+
 @item -nowindows
 @itemx -nw
 @cindex @code{--nowindows}

Re: RFC: GDB as a loader 1/3: silent batch mode

[Eli Zaretskii]

> Date: Fri, 28 Oct 2005 10:48:19 +0100
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: gdb@sources.redhat.com
> 
> Out of interest, why does 'GDB' have to be '@value{GDBN}'? What does 
> that do?

It gives us a simple way to change the name of GDB in the manual.
This is sometimes needed when one wants to produce a tailored GDB
package specific to some host/target configuration, for a specific
client, and call it by some other name to distinguish from the
standard edition.

The "@value{GDBN}" construct is a simple string substitution
mechanism: it causes makeinfo, the program that produces the Info
manual from its Texinfo sources, to replace "@value{GDBN}" with the
string that is the value of the GDBN variable.  The default value is
set in the gdb-cfg.texi file:

    @set GDBN @sc{gdb}

which is included by gdb.texinfo.  However, one could replace this
value, either in gdb-cfg.texi or by invoking makeinfo with the -D
switch, for example:

	makeinfo -DGDBN="my@sc{gdb}" gdb.texinfo

> I can create the info file fine, but the PDF has errors.

What command did you use to produce the PDF file?  Also, please send
the error messages you saw.

> The only thing 
> I can see wrong with the produced file is that the index is missing. Is 
> this a known problem or am I using the wrong version of something? I 
> have Texinfo 4.5.

I don't think it's a known problem, but perhaps you should upgrade
your Texinfo.

> Still nobody has given an opinion on any of the three patches I sent 
> adding new options. What do you want to do with them? Do we know if 
> Daniel is back from holiday yet?

I'll let Daniel answer that ;-)

> I'll do the docs for the other two options soon.

Thanks.

> +@item -batch-silent
> +@cindex @code{--batch-silent}
> +Run in batch mode exactly like @samp{-batch}, but totally silently. All
> +@value{GDBN} output to @code{stdout} is prevented (@code{stderr} is
> +unaffected).  This is much quieter than @samp{-silent} and would be useless
> +for an interactive session.
> +
> +This is particularly useful when using targets that give @samp{Loading section} messages, for example.
> +
> +Note that targets that give their output via @value{GDBN}, as opposed to
> +writing directly to @code{stdout}, will also be made silent.

This is okay, but still the first sentence has only one space after
the period that ends it.

Re: RFC: GDB as a loader 1/3: silent batch mode

[Andrew STUBBS]

[-- Attachment #1: Type: text/plain, Size: 470 bytes --]

Eli Zaretskii wrote:
> I don't think it's a known problem, but perhaps you should upgrade
> your Texinfo.

I have found a texinfo 4.7 and tried that with no more success.

I was just using: make gdb.pdf

The gdb.log file is attached. Maybe you can make more sense of it than I 
can.

> This is okay, but still the first sentence has only one space after
> the period that ends it.

Sorry. I missed that one. I can see this full-stop thing biting me many 
times.

Andrew

[-- Attachment #2: gdb.log --]
[-- Type: text/plain, Size: 19225 bytes --]

This is pdfeTeX, Version 3.14159-14h-released-20010417-2.1 (Web2C 7.3.3.1) (format=pdfetex 2005.4.3)  28 OCT 2005 14:43
entering extended mode
**/ccase/filer1/view-store/stubbsa/gdb-contribute/src/gdb/doc/gdb.texinfo
(/ccase/filer1/view-store/stubbsa/gdb-contribute/src/gdb/doc/gdb.texinfo{/usr/s
hare/texmf/pdftex/config/pdftex.cfg}
(/ccase/filer1/view-store/stubbsa/gdb-contribute/src/texinfo/texinfo.tex
Loading texinfo [version 2004-02-19.09]: Basics,
\bindingoffset=\dimen16
\normaloffset=\dimen17
\pagewidth=\dimen18
\pageheight=\dimen19
\outerhsize=\dimen20
\outervsize=\dimen21
\cornerlong=\dimen22
\cornerthick=\dimen23
\topandbottommargin=\dimen24
\headlinebox=\box16
\footlinebox=\box17
\margin=\insert252
\EMsimple=\toks13
\groupbox=\box18
\groupinvalidhelp=\toks14
\mil=\dimen25
\exdentamount=\skip18
\inmarginspacing=\skip19
 pdf,
\tempnum=\count27
\lnkcount=\count28
\filename=\toks15
\filenamelength=\count29
\pgn=\count30
\toksA=\toks16
\toksB=\toks17
\toksC=\toks18
\toksD=\toks19
\boxA=\box19
\countA=\count31

(/usr/share/texmf/pdftex/plain/misc/pdfcolor.tex) fonts,
\sffam=\fam8
\textleading=\dimen26
\mainmagstep=\count32
\fontdepth=\count33
 page headings,
\titlepagetopglue=\skip20
\titlepagebottomglue=\skip21
\evenheadline=\toks20
\oddheadline=\toks21
\evenfootline=\toks22
\oddfootline=\toks23

tables,
\tableindent=\dimen27
\itemindent=\dimen28
\itemmargin=\dimen29
\itemmax=\dimen30
\itemno=\count34
\multitableparskip=\skip22
\multitableparindent=\skip23
\multitablecolspace=\dimen31
\multitablelinespace=\skip24
\colcount=\count35
\everytab=\toks24
 conditionals,
\doignorecount=\count36
 indexing,
\secondaryindent=\skip25
\partialpage=\box20
\doublecolumnhsize=\dimen32
 sectioning,
\unnumberedno=\count37
\chapno=\count38
\secno=\count39
\subsecno=\count40
\subsubsecno=\count41
\appendixno=\count42
\absseclevel=\count43
\secbase=\count44
\chapheadingskip=\skip26
\secheadingskip=\skip27
\subsecheadingskip=\skip28
 toc,
\tocfile=\write0
\contentsrightmargin=\skip29
\savepageno=\count45
\lastnegativepageno=\count46
\tocindent=\dimen33
 environments,
\errorbox=\box21
\lispnarrowing=\skip30
\envskipamount=\skip31
\circthick=\dimen34
\cartouter=\dimen35
\cartinner=\dimen36
\normbskip=\skip32
\normpskip=\skip33
\normlskip=\skip34
\lskip=\skip35
\rskip=\skip36
\tabw=\dimen37
 defuns,
\defbodyindent=\skip37
\defargsindent=\skip38
\deflastargmargin=\skip39
\parencount=\count47
\brackcount=\count48
 macros,
\paramno=\count49
\macname=\toks25

cross references,
\auxfile=\write1
\savesfregister=\count50
 insertions,
\footnoteno=\count51
\SAVEfootins=\box22
\SAVEmargin=\box23
 (/usr/share/texmf/tex/plain/dvips/epsf.tex
\epsffilein=\read1
\epsfframemargin=\dimen38
\epsfframethickness=\dimen39
\epsfrsize=\dimen40
\epsftmp=\dimen41
\epsftsize=\dimen42
\epsfxsize=\dimen43
\epsfysize=\dimen44
\pspoints=\dimen45
\epsfnoopenhelp=\toks26
)
\noepsfhelp=\toks27
\appendtomacroAtoks=\toks28
\appendtomacroBtoks=\toks29

localization,
\nolanghelp=\toks30
\defaultparindent=\dimen46
 and turning on texinfo input format.)
\openout1 = `gdb.aux'.

@cpindfile=@write2
@fnindfile=@write3
@vrindfile=@write4
@tpindfile=@write5
@kyindfile=@write6
@pgindfile=@write7
 (./gdb-cfg.texi
(./GDBvn.texi)) [1
\openout2 = `gdb.cp'.

\openout3 = `gdb.fn'.

\openout4 = `gdb.vr'.

\openout5 = `gdb.tp'.

\openout6 = `gdb.ky'.

\openout7 = `gdb.pg'.

{/usr/share/texmf/dvips/config/pdftex.map}] [2] [-1] [-2]
(Summary of @value {GDBN})
\openout0 = `gdb.toc'.


Cross reference values unknown; you must run TeX again. [1] [2] [3] [4]
Chapter 1 [5] [6] [7] [8] [9] Chapter 2 [10] [11] [12] [13] [14] [15] [16]
Chapter 3 [17] [18] [19] [20] [21] [22] Chapter 4 [23] [24] [25] [26] [27]
[28] [29] [30] [31] [32] [33] Chapter 5 [34] [35] [36] [37] [38] [39] [40]
[41] [42] [43] [44] [45] [46] [47] [48] [49] [50] [51] [52] [53] [54]
Chapter 6 [55] [56] [57] [58] [59] [60] [61] Chapter 7 [62] [63] [64] [65]
[66] [67] Chapter 8 [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78]
[79] [80] [81] [82] [83] [84] [85] [86] [87] [88] [89] [90] Chapter 9 [91]
[92] [93] [94] [95] Chapter 10 [96] [97] [98] [99] [100] [101] [102] [103]
Chapter 11 [104] [105] [106] [107] [108] Chapter 12 [109] [110] [111] [112]
[113] [114] [115] [116] [117] [118] [119] [120] [121] [122] [123] [124]
[125] [126] [127] [128] [129] Chapter 13 [130] [131] [132] [133] [134]
Chapter 14 [135] [136] [137] [138] [139] [140] Chapter 15 [141] [142] [143]
[144] [145] [146] [147] [148]
Underfull \hbox (badness 2310) in paragraph at lines 11140--11147
 /cmr10@10.95pt/fails to lo-cate the li-brary, or if the path to the li-brary i
s rel-a-tive

@hbox(7.60416+2.12917)x433.62, glue set 2.84929
.@glue(@leftskip) 57.81621
./cmr10@10.95pt/f
./cmr10@10.95pt/a
./cmr10@10.95pt/i
./cmr10@10.95pt/l
.etc.


Underfull \hbox (badness 5533) in paragraph at lines 11184--11187
 []/cmr10@10.95pt/a sub-di-rec-tory of that di-rec-tory named `/cmtt10@10.95pt/
.debug[]/cmr10@10.95pt/'[] (that is, the file `/cmsltt10@10.95pt/ex-

@hbox(8.2125+2.73749)x433.62, glue set 3.81364
.@glue(@leftskip) 21.68121
.@hbox(4.86667+0.0)x0.0, glue set - 12.70244fil
..@glue 0.0 plus 1.0fil minus 1.0fil
..@mathon
../cmsy10@10.95pt/^^O
..@mathoff
..@kern 7.22743
./cmr10@10.95pt/a
.@glue 3.65 plus 1.825 minus 1.21666
./cmr10@10.95pt/s
.etc.

[149] [150] [151] Chapter 16 [152] [153] [154] [155] [156] Chapter 17 [157]
[158] [159] [160] [161] [162] [163] [164] [165] [166] [167] Chapter 18 [168]
[169] [170] [171] [172]
Underfull \hbox (badness 10000) in paragraph at lines 13006--13012
 []/cmr10@10.95pt/This com-mand dis-plays in-for-ma-tion re-turned by the Win32
 API

@hbox(7.60416+2.12917)x433.62, glue set 4.5858
.@glue(@leftskip) 57.81621
.@hbox(0.0+0.0)x0.0
./cmr10@10.95pt/T
./cmr10@10.95pt/h
./cmr10@10.95pt/i
.etc.

[173] [174] [175] [176] [177] [178] [179] [180] [181] [182] [183] [184]
[185] [186] [187] [188]
Underfull \hbox (badness 10000) in paragraph at lines 14348--14349
 []/cmtt10@10.95pt/hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var)
 &&

@hbox(7.60416+2.43333)x433.62
.@glue(@leftskip) 57.81621
.@hbox(0.0+0.0)x0.0
./cmtt10@10.95pt/h
./cmtt10@10.95pt/w
./cmtt10@10.95pt/a
.etc.


Underfull \hbox (badness 10000) in paragraph at lines 14350--14351
 []/cmtt10@10.95pt/hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var)
 &&

@hbox(7.60416+2.43333)x433.62
.@glue(@leftskip) 57.81621
.@hbox(0.0+0.0)x0.0
./cmtt10@10.95pt/h
./cmtt10@10.95pt/w
./cmtt10@10.95pt/a
.etc.

[189] [190] [191] [192] [193] [194] [195] [196] Chapter 19 [197] [198] [199]
[200] [201] [202] [203] [204] [205] Chapter 20 [206] [207] [208] [209]
Chapter 21 [210] Chapter 22 [211] [212] [213] [214] [215] [216] Chapter 23
[217] [218] [219] Chapter 24 [220] [221] [222] [223] [224] [225] [226] [227]
[228] [229] [230] [231] [232] [233] [234] [235] [236] [237] [238] [239]
[240] [241] [242] [243] [244] [245] [246] [247] [248] [249] [250] [251]
[252] [253] [254] [255] [256] [257] [258] [259] [260] [261] [262] [263]
[264] [265] [266] [267] [268] [269] [270] [271]
! Missing @endcsname inserted.
<to be read again> 
                   @discretionary 
-->-@discretionary 
                   {}{}{}
<argument> -
            var-list-children
@xrefX ...@expandafter @Xthisreftitle @csname XR#1
                                                  -title@endcsname }@iffloat...

@tclose ...enation @rawbackslash @frenchspacing #1
                                                  }@null 
@codex #1->@tclose {#1}
                       @endgroup 
l.20688 @code{@pxref{-var-list-children}}
                                         .
? q
OK, entering @batchmode...
! Extra @endcsname.
@xrefX ...isreftitle @csname XR#1-title@endcsname 
                                                  }@iffloat @Xthisreftitle @...

@tclose ...enation @rawbackslash @frenchspacing #1
                                                  }@null 
@codex #1->@tclose {#1}
                       @endgroup 
l.20688 @code{@pxref{-var-list-children}}
                                         .
I'm ignoring this, since I wasn't doing a \csname.

! Missing @endcsname inserted.
<to be read again> 
                   @discretionary 
-->-@discretionary 
                   {}{}{}
<argument> -
            var-list-children-snt
@refx ... @let @expandafter @thisrefX @csname XR#1
                                                  @endcsname }@ifx @thisrefX...

@xrefX ... = @hbox {@ignorespaces @refx {#1-snt}{}
                                                  }@ifdim @wd 2 > 0pt @refx ...

@tclose ...enation @rawbackslash @frenchspacing #1
                                                  }@null 
...
l.20688 @code{@pxref{-var-list-children}}
                                         .
The control sequence marked <to be read again> should
not appear between \csname and \endcsname.

! Extra @endcsname.
@refx ...ndafter @thisrefX @csname XR#1@endcsname 
                                                  }@ifx @thisrefX @relax @an...

@xrefX ... = @hbox {@ignorespaces @refx {#1-snt}{}
                                                  }@ifdim @wd 2 > 0pt @refx ...

@tclose ...enation @rawbackslash @frenchspacing #1
                                                  }@null 
@codex #1->@tclose {#1}
                       @endgroup 
l.20688 @code{@pxref{-var-list-children}}
                                         .
I'm ignoring this, since I wasn't doing a \csname.

! Missing @endcsname inserted.
<to be read again> 
                   @discretionary 
-->-@discretionary 
                   {}{}{}
<argument> -
            var-list-children-snt
@refx ... @let @expandafter @thisrefX @csname XR#1
                                                  @endcsname }@ifx @thisrefX...

@xrefX ...@ifdim @wd 2 > 0pt @refx {#1-snt}@space 
                                                  @fi }@xrefprintnodename @p...

@tclose ...enation @rawbackslash @frenchspacing #1
                                                  }@null 
...
l.20688 @code{@pxref{-var-list-children}}
                                         .
The control sequence marked <to be read again> should
not appear between \csname and \endcsname.

! Extra @endcsname.
@refx ...ndafter @thisrefX @csname XR#1@endcsname 
                                                  }@ifx @thisrefX @relax @an...

@xrefX ...@ifdim @wd 2 > 0pt @refx {#1-snt}@space 
                                                  @fi }@xrefprintnodename @p...

@tclose ...enation @rawbackslash @frenchspacing #1
                                                  }@null 
@codex #1->@tclose {#1}
                       @endgroup 
l.20688 @code{@pxref{-var-list-children}}
                                         .
I'm ignoring this, since I wasn't doing a \csname.

! Missing @endcsname inserted.
<to be read again> 
                   @discretionary 
-->-@discretionary 
                   {}{}{}
<argument> -
            var-list-children-pg
@refx ... @let @expandafter @thisrefX @csname XR#1
                                                  @endcsname }@ifx @thisrefX...

@xrefX ...kslash @putwordpage @tie @refx {#1-pg}{}
                                                  @fi @fi @endlink @endgroup 
@tclose ...enation @rawbackslash @frenchspacing #1
                                                  }@null 
...
l.20688 @code{@pxref{-var-list-children}}
                                         .
The control sequence marked <to be read again> should
not appear between \csname and \endcsname.

! Extra @endcsname.
@refx ...ndafter @thisrefX @csname XR#1@endcsname 
                                                  }@ifx @thisrefX @relax @an...

@xrefX ...kslash @putwordpage @tie @refx {#1-pg}{}
                                                  @fi @fi @endlink @endgroup 
@tclose ...enation @rawbackslash @frenchspacing #1
                                                  }@null 
@codex #1->@tclose {#1}
                       @endgroup 
l.20688 @code{@pxref{-var-list-children}}
                                         .
I'm ignoring this, since I wasn't doing a \csname.


Underfull \hbox (badness 10000) in paragraph at lines 20683--20689
/cmtt10@10.95pt/children-titlevar-list-children-snt$/cmsy10@10.95pt/h$/cmtt10@1
0.95pt/undefined$/cmsy10@10.95pt/i$ /cmtt10@10.95pt/[-var-list-children],

@hbox(8.2125+2.73749)x433.62
./cmtt10@10.95pt/c
./cmtt10@10.95pt/h
./cmtt10@10.95pt/i
./cmtt10@10.95pt/l
./cmtt10@10.95pt/d
.etc.

 Chapter 25 [272] [273] [274] [275] Chapter 26 [276] [277] [278]
(/ccase/filer1/view-store/stubbsa/gdb-contribute/src/readline/doc/rluser.texinf
o
@btindfile=@write8
 Chapter 27 [279
\openout8 = `gdb.bt'.

] [280] [281] [282] [283] [284] [285]
Underfull \hbox (badness 4217) in paragraph at lines 483--487
 /cmr10@10.95pt/search with-out sub-se-quently ex-e-cut-ing the char-ac-ter as 
a

@hbox(7.60416+2.12917)x433.62, glue set 3.48424
.@glue(@leftskip) 115.63242
./cmr10@10.95pt/s
./cmr10@10.95pt/e
./cmr10@10.95pt/a
./cmr10@10.95pt/r
.etc.


Underfull \hbox (badness 5231) in paragraph at lines 488--504
 /cmtt10@10.95pt/emacs-meta[]/cmr10@10.95pt/, /cmtt10@10.95pt/emacs-ctlx[]/cmr1
0@10.95pt/, /cmtt10@10.95pt/vi[]/cmr10@10.95pt/, /cmtt10@10.95pt/vi-move[]/cmr1
0@10.95pt/, /cmtt10@10.95pt/vi-command[]/cmr10@10.95pt/, and

@hbox(7.60416+2.12917)x433.62, glue set 3.7426
.@glue(@leftskip) 115.63242
./cmtt10@10.95pt/e
./cmtt10@10.95pt/m
./cmtt10@10.95pt/a
./cmtt10@10.95pt/c
.etc.

 [286] [287] [288] [289]
Overfull \hbox (26.43913pt too wide) in paragraph at lines 790--790
 []/cmtt10@10.95pt/Meta-Control-h: backward-kill-word Text after the function n
ame is ignored[] 

@hbox(6.69167+2.43333)x433.62
.@glue(@leftskip) 28.90755
.@hbox(0.0+0.0)x0.0
./cmtt10@10.95pt/M
./cmtt10@10.95pt/e
./cmtt10@10.95pt/t
.etc.

 [290] [291] [292] [293] [294] [295] [296] [297])
(/ccase/filer1/view-store/stubbsa/gdb-contribute/src/readline/doc/inc-hist.texi
nfo Chapter 28 [298] [299] [300]) Appendix A [301] [302] [303] Appendix B [304]

Underfull \hbox (badness 10000) in paragraph at lines 21363--21365
[]/cmr10@10.95pt/For ex-am-ple, the /cmcsc10@10.95pt/gdb /cmr10@10.95pt/ver-sio
n 6.3.50.20051028-cvs dis-tri-bu-tion is in the

@hbox(7.60416+2.12917)x433.62, glue set 4.58098
.@hbox(0.0+0.0)x15.0
./cmr10@10.95pt/F
.@kern-0.91252
./cmr10@10.95pt/o
./cmr10@10.95pt/r
.etc.


Underfull \hbox (badness 4120) in paragraph at lines 21395--21398
[]/cmr10@10.95pt/The sim-plest way to con-fig-ure and build /cmcsc10@10.95pt/gd
b /cmr10@10.95pt/is to run /cmtt10@10.95pt/configure[] /cmr10@10.95pt/from

@hbox(7.60416+2.43333)x433.62, glue set 3.4562
.@hbox(0.0+0.0)x15.0
./cmr10@10.95pt/T
./cmr10@10.95pt/h
./cmr10@10.95pt/e
.@glue 3.65 plus 1.825 minus 1.21666
.etc.


Underfull \hbox (badness 10000) in paragraph at lines 21395--21398
/cmr10@10.95pt/the `/cmtt10@10.95pt/gdb-/cmsltt10@10.95pt/version-number[]/cmr1
0@10.95pt/'[] source di-rec-tory, which in this ex-am-ple is the

@hbox(7.60416+2.43333)x433.62, glue set 4.94301
./cmr10@10.95pt/t
./cmr10@10.95pt/h
./cmr10@10.95pt/e
.@glue 3.65 plus 1.825 minus 1.21666
./cmr10@10.95pt/`
.etc.

 [305] [306] [307] Appendix C [308] [309]
Underfull \hbox (badness 8038) in paragraph at lines 21793--21799
 []/cmr10@10.95pt/The com-mand /cmtt10@10.95pt/maint print raw-registers[] /cmr
10@10.95pt/in-cludes the con-tents of

@hbox(7.60416+2.43333)x433.62, glue set 4.31732
.@glue(@leftskip) 57.81621
.@hbox(0.0+0.0)x0.0
./cmr10@10.95pt/T
./cmr10@10.95pt/h
./cmr10@10.95pt/e
.etc.


Underfull \hbox (badness 3492) in paragraph at lines 21793--21799
 /cmr10@10.95pt/the raw reg-is-ter cache; the com-mand /cmtt10@10.95pt/maint pr
int cooked-registers[]

@hbox(7.60416+2.43333)x433.62, glue set 3.27243
.@glue(@leftskip) 57.81621
./cmr10@10.95pt/t
./cmr10@10.95pt/h
./cmr10@10.95pt/e
.@glue 3.65 plus 1.825 minus 1.21666
.etc.

 [310] [311] [312] Appendix D [313] [314] [315] [316]
Underfull \hbox (badness 10000) in paragraph at lines 22196--22203
 /cmsl10@10.95pt/RE-CATED[]REGISTER[]RAW[]SIZE /cmr10@10.95pt/and /cmsl10@10.95
pt/REG-IS-TER[]NAME

@hbox(7.60416+0.0)x433.62, glue set 5.2506
.@glue(@leftskip) 115.63242
./cmsl10@10.95pt/R
./cmsl10@10.95pt/E
.@discretionary
../cmsl10@10.95pt/-
./cmsl10@10.95pt/C
.etc.

 [317] [318] [319] [320] [321] [322] [323] [324] [325]
Underfull \hbox (badness 3735) in paragraph at lines 22906--22909
 []/cmr10@10.95pt/The tar-get re-quests the value of sym-bol /cmsl10@10.95pt/sy
m[]name /cmr10@10.95pt/(hex

@hbox(8.2125+2.73749)x433.62, glue set 3.34543
.@glue(@leftskip) 115.63242
.@hbox(0.0+0.0)x0.0
./cmr10@10.95pt/T
./cmr10@10.95pt/h
./cmr10@10.95pt/e
.etc.


Underfull \hbox (badness 6775) in paragraph at lines 22906--22909
 /cmr10@10.95pt/en-coded). /cmcsc10@10.95pt/gdb /cmr10@10.95pt/may pro-vide the
 value by us-ing the

@hbox(8.2125+2.73749)x433.62, glue set 4.07831
.@glue(@leftskip) 115.63242
./cmr10@10.95pt/e
./cmr10@10.95pt/n
.@discretionary
../cmr10@10.95pt/-
./cmr10@10.95pt/c
.etc.


Underfull \hbox (badness 4765) in paragraph at lines 22941--22944
 []/cmr10@10.95pt/Here are the spe-cific re-quests of this form de-fined so far
. All

@hbox(7.60416+2.12917)x433.62, glue set 3.62845
.@glue(@leftskip) 57.81621
.@hbox(0.0+0.0)x0.0
./cmr10@10.95pt/H
./cmr10@10.95pt/e
./cmr10@10.95pt/r
.etc.

 [326] [327] [328] [329] [330] [331] [332] [333] [334] [335] [336] [337] [338] 
[339]
(/ccase/filer1/view-store/stubbsa/gdb-contribute/src/gdb/doc/agentexpr.texi App
endix E [340] [341] [342] [343] [344] [345] [346] [347] [348] [349] [350] [351]
)
(/ccase/filer1/view-store/stubbsa/gdb-contribute/src/gdb/doc/gpl.texi Appendix 
F [352] [353] [354] [355] [356] [357])
(/ccase/filer1/view-store/stubbsa/gdb-contribute/src/gdb/doc/fdl.texi Appendix 
G [358] [359] [360] [361] [362] [363] [364]) (Index) [365] [366] [367] [368] ) 
Here is how much of TeX's memory you used:
 2716 strings out of 22362
 31545 string characters out of 213452
 71710 words of memory out of 350001
 3071 multiletter control sequences out of 10000+15000
 32127 words of font info for 112 fonts, out of 400000 for 1000
 47 hyphenation exceptions out of 10000
 18i,7n,16p,298b,442s stack positions out of 3000i,100n,1500p,50000b,4000s

! pdfTeX warning (dest): name{-\discretionary {}{}{}var-\discretionary {}{}{}li
st-\discretionary {}{}{}children} has been referenced but does not exist, repla
ced by a fixed one

</usr/share/texmf/fonts/type1/bluesky/cm/cmss10.pfb></usr/share/texmf/fonts/typ
e1/bluesky/cm/cmtt12.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cmsl9.pfb></u
sr/share/texmf/fonts/type1/bluesky/cm/cmr8.pfb></usr/share/texmf/fonts/type1/bl
uesky/cm/cmsy9.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cmr9.pfb></usr/shar
e/texmf/fonts/type1/bluesky/cm/cmr7.pfb></usr/share/texmf/fonts/type1/bluesky/c
m/cmsltt10.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cmtt9.pfb></usr/share/t
exmf/fonts/type1/bluesky/cm/cmb10.pfb></usr/share/texmf/fonts/type1/bluesky/cm/
cmsl10.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cmtt10.pfb></usr/share/texm
f/fonts/type1/bluesky/cm/cmsy10.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cm
ti10.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cmr10.pfb></usr/share/texmf/f
onts/type1/bluesky/cm/cmcsc10.pfb></usr/share/texmf/fonts/type1/bluesky/cm/cmbx
12.pfb>
Output written on gdb.pdf (372 pages, 1356623 bytes).

[-- Attachment #3: batch-silent-docs.patch --]
[-- Type: text/plain, Size: 1067 bytes --]

2005-10-28  Andrew Stubbs  <andrew.stubbs@st.com>

	* gdb.texinfo (Choosing modes): Add --batch-silent.

Index: src/gdb/doc/gdb.texinfo
===================================================================
--- src.orig/gdb/doc/gdb.texinfo	2005-10-28 13:05:46.000000000 +0100
+++ src/gdb/doc/gdb.texinfo	2005-10-28 14:04:49.000000000 +0100
@@ -994,6 +994,18 @@ Program exited normally.
 @value{GDBN} control terminates) is not issued when running in batch
 mode.
 
+@item -batch-silent
+@cindex @code{--batch-silent}
+Run in batch mode exactly like @samp{-batch}, but totally silently.  All
+@value{GDBN} output to @code{stdout} is prevented (@code{stderr} is
+unaffected).  This is much quieter than @samp{-silent} and would be useless
+for an interactive session.
+
+This is particularly useful when using targets that give @samp{Loading section} messages, for example.
+
+Note that targets that give their output via @value{GDBN}, as opposed to
+writing directly to @code{stdout}, will also be made silent.
+
 @item -nowindows
 @itemx -nw
 @cindex @code{--nowindows}

Re: RFC: GDB as a loader 1/3: silent batch mode

[Eli Zaretskii]

> Date: Fri, 28 Oct 2005 14:55:57 +0100
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: gdb@sources.redhat.com
> 
> I was just using: make gdb.pdf
> 
> The gdb.log file is attached. Maybe you can make more sense of it than I 
> can.

I think I fixed the problem that caused this, but I cannot verify
right now, since I don't have the necessary stuff installed where I
type this.  Could you please resync with the CVS repository and try
"make gdb.pdf" again?

Re: RFC: GDB as a loader 1/3: silent batch mode

[Andrew STUBBS]

Eli Zaretskii wrote:
> I think I fixed the problem that caused this, but I cannot verify
> right now, since I don't have the necessary stuff installed where I
> type this.  Could you please resync with the CVS repository and try
> "make gdb.pdf" again?

That fixed it. Thanks

Re: RFC: GDB as a loader 1/3: silent batch mode

[Daniel Jacobowitz]

On Fri, Oct 28, 2005 at 07:23:18PM +0200, Eli Zaretskii wrote:
> > Date: Fri, 28 Oct 2005 14:55:57 +0100
> > From: Andrew STUBBS <andrew.stubbs@st.com>
> > Cc: gdb@sources.redhat.com
> > 
> > I was just using: make gdb.pdf
> > 
> > The gdb.log file is attached. Maybe you can make more sense of it than I 
> > can.
> 
> I think I fixed the problem that caused this, but I cannot verify
> right now, since I don't have the necessary stuff installed where I
> type this.  Could you please resync with the CVS repository and try
> "make gdb.pdf" again?

Hi Eli,

Could you please post the patch to gdb-patches?  That's our standard
practice for every change, no matter how trivial.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: RFC: GDB as a loader 1/3: silent batch mode

[Daniel Jacobowitz]

On Fri, Oct 28, 2005 at 02:49:23PM +0200, Eli Zaretskii wrote:
> > Still nobody has given an opinion on any of the three patches I sent 
> > adding new options. What do you want to do with them? Do we know if 
> > Daniel is back from holiday yet?
> 
> I'll let Daniel answer that ;-)

I am back, but was busy all week.  I'll try to review them this
weekend.  I was sort of hoping that one of the other maintainers felt
like it while I was away...

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: RFC: GDB as a loader 1/3: silent batch mode

[Daniel Jacobowitz]

Please send patches, even RFC patches, to gdb-patches; I try to keep
code review off of gdb@.  Redirecting there.

On Tue, Oct 18, 2005 at 12:26:55PM +0100, Andrew STUBBS wrote:
> All have been regression tested for both i686-pc-linux-gnu and sh-elf an
> have produced no new failures. I have not attempted to produce any new
> test cases. Probably there should be some, but where and how?

They would be nice... but for this one in particular, I think it's not
worth the trouble.  It would require some TCL magic.

> Silent Batch Mode
> 
> The attached patch implements a new option --batch-silent. This does
> much the same a --batch, except that it also disables gdb_stdout. This
> means that all GDB outputs, other than errors, are hidden.
> 
> The advantage of this is that I no longer have to create dodgy scripts
> to filter out all the various GDB messages from my program output
> (Loading section ..., Process exited successfully, etc.).
> 
> Obviously this is not particularly useful with targets such as the GDB
> simulator that give their output through the GDB print mechanisms.
> However, all targets which print via regular stdout (as our custom
> target interface here at ST does) work fine. Perhaps somebody could
> suggest a solution for those targets with which it does not work.

That sounds like just a new variant of the MI inferior-io-mixed-in
problem.  Perhaps it could share a solution.

In the mean time, along with the documentation that Eli has already
approved, this patch is OK; please wrap the one really long line the
texinfo, though.

> 2005-10-18  Andrew Stubbs  <andrew.stubbs@st.com>
> 
>         * event-top.c (gdb_setup_readline): Don't set gdb_stdout when
>         --batch-silent option was given.
>         * main.c (batch_silent): New variable.
>         (captured_main): Add new option --batch-silent.
>         (print_gdb_help): Likewise.

OK.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: RFC: GDB as a loader 1/3: silent batch mode

[Eli Zaretskii]

> Date: Fri, 28 Oct 2005 18:33:32 +0100
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: gdb@sources.redhat.com
> 
> Eli Zaretskii wrote:
> > I think I fixed the problem that caused this, but I cannot verify
> > right now, since I don't have the necessary stuff installed where I
> > type this.  Could you please resync with the CVS repository and try
> > "make gdb.pdf" again?
> 
> That fixed it. Thanks

Thanks for testing (and for paying attention to the problem in the
first place).

Re: RFC: GDB as a loader 1/3: silent batch mode

[Eli Zaretskii]

> Date: Fri, 28 Oct 2005 16:38:36 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Andrew STUBBS <andrew.stubbs@st.com>, gdb@sources.redhat.com
> 
> On Fri, Oct 28, 2005 at 07:23:18PM +0200, Eli Zaretskii wrote:
> > > Date: Fri, 28 Oct 2005 14:55:57 +0100
> > > From: Andrew STUBBS <andrew.stubbs@st.com>
> > > Cc: gdb@sources.redhat.com
> > > 
> > > I was just using: make gdb.pdf
> > > 
> > > The gdb.log file is attached. Maybe you can make more sense of it than I 
> > > can.
> > 
> > I think I fixed the problem that caused this, but I cannot verify
> > right now, since I don't have the necessary stuff installed where I
> > type this.  Could you please resync with the CVS repository and try
> > "make gdb.pdf" again?
> 
> Hi Eli,
> 
> Could you please post the patch to gdb-patches?  That's our standard
> practice for every change, no matter how trivial.

Sorry, forgot about that.  Here it is.  As you see, it was incorrect
usage of @pxref.


2005-10-28  Eli Zaretskii  <eliz@gnu.org>

	* gdb.texinfo (GDB/MI Variable Objects): Fix @pxref usage under
	"The -var-update Command".

Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.280
retrieving revision 1.281
diff -u -r1.280 -r1.281
--- gdb/doc/gdb.texinfo	3 Oct 2005 22:26:54 -0000	1.280
+++ gdb/doc/gdb.texinfo	28 Oct 2005 17:20:03 -0000	1.281
@@ -20636,9 +20636,9 @@
 Update the value of the variable object @var{name} by evaluating its
 expression after fetching all the new values from memory or registers.
 A @samp{*} causes all existing variable objects to be updated.  The
-option @var{print-values} determines whether names and values, or just
-names are printed in the manner described for
-@code{@pxref{-var-list-children}}.
+option @var{print-values} determines whether names both and values, or
+just names are printed in the manner described for
+@code{-var-list-children} (@pxref{-var-list-children}).
 
 @subsubheading Example