From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15445 invoked by alias); 20 May 2010 16:47:02 -0000 Received: (qmail 15420 invoked by uid 22791); 20 May 2010 16:46:58 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 20 May 2010 16:46:52 +0000 Received: (qmail 1532 invoked from network); 20 May 2010 16:46:50 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 20 May 2010 16:46:50 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [rfa] gdb.base/volatile.exp / varargs.exp: replace send_gdb with gdb_test Date: Thu, 20 May 2010 16:47:00 -0000 User-Agent: KMail/1.12.2 (Linux/2.6.31-21-generic; KDE/4.3.2; x86_64; ; ) Cc: Joel Brobecker , Michael Snyder References: <4BF4497E.9040209@vmware.com> <201005201724.42637.pedro@codesourcery.com> <20100520163130.GB3019@adacore.com> In-Reply-To: <20100520163130.GB3019@adacore.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201005201746.48113.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-05/txt/msg00423.txt.bz2 On Thursday 20 May 2010 17:31:30, Joel Brobecker wrote: > > something like this is used in several places in the > > testsuite. we could perhaps add a wrapper in gdb.exp. > > I think we should - it's something that is so common, and the > gdb.reverse section alone is littered with FIXMEs because of > this issue. Yeah, I pointed this out before in that context, and also pointed out in that context that for "set foo", we could try "show foo", and confirm that what we tried to set actually was set. Similarly for any test that should produce no output and that has a corresponding "state getter". > gdb_test_no_output? Sounds good. -- Pedro Alves