From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12588 invoked by alias); 23 Feb 2011 03:46:38 -0000 Received: (qmail 12580 invoked by uid 22791); 23 Feb 2011 03:46:37 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 23 Feb 2011 03:46:33 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id AF2212BAC3D; Tue, 22 Feb 2011 22:46:31 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id i1YQxdoX7FW8; Tue, 22 Feb 2011 22:46:31 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 27EC12BAB5C; Tue, 22 Feb 2011 22:46:31 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 873321459B0; Wed, 23 Feb 2011 07:46:22 +0400 (RET) Date: Wed, 23 Feb 2011 04:01:00 -0000 From: Joel Brobecker To: Michael Snyder Cc: Tom Tromey , "gdb-patches@sourceware.org" , Vladimir Prus , "dan@codesourcery.com" Subject: Re: [RFA] add test for memattr, use get_number_or_range for memattr commands Message-ID: <20110223034622.GS2600@adacore.com> References: <4D605267.8030708@vmware.com> <20110221091304.GB2600@adacore.com> <4D62EE87.6040902@vmware.com> <20110222082747.GQ2600@adacore.com> <4D63F936.2000505@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D63F936.2000505@vmware.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2011-02/txt/msg00633.txt.bz2 > Hmmm, how about if I initialize mem1start etc. to -1? > Then the rest of the tests will fail but not crash. > Is that better? Yep, that would work for me. You could also do something like this: if {![info exists mem1start] || ![info exists mem2start] ...} { fail "..." # No point in continuing the rest of the testcase if we couldn't # get the addresses we need bla bla bla. return } -- Joel