From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20976 invoked by alias); 27 Oct 2005 17:57:15 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 20922 invoked by uid 22791); 27 Oct 2005 17:57:05 -0000 Received: from lon-del-02.spheriq.net (HELO lon-del-02.spheriq.net) (195.46.50.98) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 27 Oct 2005 17:57:05 +0000 Received: from lon-out-02.spheriq.net ([195.46.50.130]) by lon-del-02.spheriq.net with ESMTP id j9RHutZB001378 for ; Thu, 27 Oct 2005 17:56:55 GMT Received: from lon-cus-02.spheriq.net (lon-cus-02.spheriq.net [195.46.50.38]) by lon-out-02.spheriq.net with ESMTP id j9RHus8S012496 for ; Thu, 27 Oct 2005 17:56:54 GMT Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by lon-cus-02.spheriq.net with ESMTP id j9RHuqlh001249 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Thu, 27 Oct 2005 17:56:53 GMT Received: from zeta.dmz-eu.st.com (ns2.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 88B7BDA41; Thu, 27 Oct 2005 17:56:48 +0000 (GMT) Received: by zeta.dmz-eu.st.com (STMicroelectronics, from userid 60012) id E181047487; Thu, 27 Oct 2005 17:59:37 +0000 (GMT) Received: from zeta.dmz-eu.st.com (localhost [127.0.0.1]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 985E575999; Thu, 27 Oct 2005 17:59:37 +0000 (UTC) Received: from mail1.bri.st.com (mail1.bri.st.com [164.129.8.218]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 2655E47450; Thu, 27 Oct 2005 17:59:37 +0000 (GMT) Received: from [164.129.15.13] (terrorhawk.bri.st.com [164.129.15.13]) by mail1.bri.st.com (MOS 3.5.8-GR) with ESMTP id CEL01129 (AUTH "andrew stubbs"); Thu, 27 Oct 2005 18:56:46 +0100 (BST) Message-ID: <43611474.7070609@st.com> Date: Thu, 27 Oct 2005 17:57:00 -0000 From: Andrew STUBBS User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: Eli Zaretskii Cc: gdb@sources.redhat.com Subject: Re: RFC: GDB as a loader 1/3: silent batch mode References: <4354DBFF.7000601@st.com> In-Reply-To: Content-Type: multipart/mixed; boundary="------------050807070201080500040205" X-O-Spoofed: Not Scanned X-O-General-Status: No X-O-Spam1-Status: Not Scanned X-O-Spam2-Status: Not Scanned X-O-URL-Status: Not Scanned X-O-Virus1-Status: No X-O-Virus2-Status: Not Scanned X-O-Virus3-Status: No X-O-Virus4-Status: No X-O-Virus5-Status: Not Scanned X-O-Image-Status: Not Scanned X-O-Attach-Status: Not Scanned X-SpheriQ-Ver: 4.1.07 X-SW-Source: 2005-10/txt/msg00168.txt.bz2 This is a multi-part message in MIME format. --------------050807070201080500040205 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-length: 501 Eli Zaretskii wrote: >>Date: Tue, 18 Oct 2005 12:26:55 +0100 >>From: Andrew STUBBS >> >>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 --------------050807070201080500040205 Content-Type: text/plain; name="batch-silent-docs.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="batch-silent-docs.patch" Content-length: 1047 2005-10-27 Andrew Stubbs * 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} --------------050807070201080500040205--