From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12073 invoked by alias); 2 Sep 2003 18:35:02 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 12013 invoked from network); 2 Sep 2003 18:34:55 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 2 Sep 2003 18:34:55 -0000 Received: from redhat.com (toocool.toronto.redhat.com [172.16.14.72]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 98713800338; Tue, 2 Sep 2003 14:34:49 -0400 (EDT) Message-ID: <3F54E2C9.6050006@redhat.com> Date: Tue, 02 Sep 2003 18:35:00 -0000 From: "J. Johnston" Organization: Red Hat Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andreas Schwab Cc: Michael Snyder , gdb-patches@sources.redhat.com Subject: Re: RFA: patch to ignore dump.exp for ia64 References: <3F4673A0.3040507@redhat.com> <3F46823D.2070006@redhat.com> <3F4A7C44.4080407@redhat.com> <3F4CF346.1010408@redhat.com> <3F4CF4EB.5090408@redhat.com> <3F4E4542.3080709@redhat.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-09/txt/msg00006.txt.bz2 Andreas Schwab wrote: > "J. Johnston" writes: > > >>Index: gdb.base/dump.exp >>=================================================================== >>RCS file: /cvs/src/src/gdb/testsuite/gdb.base/dump.exp,v >>retrieving revision 1.3 >>diff -u -r1.3 dump.exp >>--- gdb.base/dump.exp 2 Jun 2003 15:51:24 -0000 1.3 >>+++ gdb.base/dump.exp 28 Aug 2003 18:00:55 -0000 >>@@ -33,12 +33,18 @@ >> set binfile ${objdir}/${subdir}/${testfile} >> set options {debug} >> >>+set is64bitonly "no" >>+ > > > Why not just using 0/1 instead of "no"/"yes"? > > Andreas. > Just a matter of arbitrary choice. The lines I based it on were using strings. It certainly isn't misleading or incorrect. -- Jeff J.