From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-33255-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 21692 invoked by alias); 3 Nov 2008 20:06:37 -0000
Received: (qmail 21600 invoked by uid 22791); 3 Nov 2008 20:06:36 -0000
X-Spam-Check-By: sourceware.org
Received: from mx1a.swcp.com (HELO mx1a.swcp.com) (216.184.2.64)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 03 Nov 2008 20:05:51 +0000
Received: from ame7.swcp.com (ame7.swcp.com [216.184.2.70]) 	by mx1a.swcp.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id mA3K5k7n005992; 	Mon, 3 Nov 2008 13:05:46 -0700
Received: from swcp.com (nousagi.swcp.com [216.184.2.107] (may be forged)) 	by ame7.swcp.com (8.14.2/8.13.6) with SMTP id mA3K5hH1021864; 	Mon, 3 Nov 2008 13:05:43 -0700 (MST) 	(envelope-from ebo@sandien.com)
Date: Mon, 03 Nov 2008 20:06:00 -0000
To: <ebo@sandien.com>, "Michael Snyder" <msnyder@vmware.com>
Subject: Re: using gdb to do embedded unit/regression testing
From: "EBo" <ebo@sandien.com>
X-Mailer: TWIG 2.7.7
Message-ID: <twig.1225742743.128@swcp.com>
In-Reply-To: <twig.1225741771.58340@swcp.com>
References: <twig.1225739451.50844@swcp.com>, <twig.1225739451.50844@swcp.com>, <490F4EAB.206@vmware.com>
X-Client-IP: 216.184.15.167
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Reply-To: ebo@sandien.com
X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (ame7.swcp.com [216.184.2.128]); Mon, 03 Nov 2008 13:05:44 -0700 (MST)
X-Virus-Status: Clean
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-11/txt/msg00020.txt.bz2

EBo <ebo@sandien.com> said:

> Michael Snyder <msnyder@vmware.com> said:
> 
> > EBo wrote:
> >
> > > The second issue will be cleaning up and formatting the output from the
> > > automated unit/regression test suites.  For this I will want/need to
suppress
> > > almost all output from gdb, and use the print command above to deal with the
> > > formatting.  If I end up using gdb to help do this type of eXtreme/Agile
> > > program testing I would like to work with the gdb maintainers to have it
> > > integrated upstream...
> > 
> > I think you want dejagnu.

I will look into dejagnu, but to follow in the original thought...

If I provided a --batch-mostly-silent switch which suppressed output for all
but the print, printf, and echo commands, would others find that useful? 
Actually I should also if someone already provides this functionality before I
start trying to modify gdb ;-)


  EBo --