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

[Andrew STUBBS <andrew.stubbs@st.com>]

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