From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26260 invoked by alias); 28 Oct 2005 20:47:51 -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 26228 invoked by uid 22791); 28 Oct 2005 20:47:46 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 28 Oct 2005 20:47:46 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EVb8b-00015S-16; Fri, 28 Oct 2005 16:47:45 -0400 Date: Fri, 28 Oct 2005 20:47:00 -0000 From: Daniel Jacobowitz To: Andrew STUBBS Cc: gdb@sources.redhat.com Subject: Re: RFC: GDB as a loader 1/3: silent batch mode Message-ID: <20051028204744.GC3849@nevyn.them.org> Mail-Followup-To: Andrew STUBBS , gdb@sources.redhat.com References: <4354DBFF.7000601@st.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4354DBFF.7000601@st.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-10/txt/msg00195.txt.bz2 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 > > * 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