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

[Andrew STUBBS <andrew dot stubbs at st dot com>]

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
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}