From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16681 invoked by alias); 12 Jan 2011 12:30:18 -0000 Received: (qmail 16654 invoked by uid 22791); 12 Jan 2011 12:30:15 -0000 X-SWARE-Spam-Status: No, hits=-5.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 12 Jan 2011 12:30:10 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id p0CCTo6q018650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 12 Jan 2011 07:29:51 -0500 Received: from localhost.localdomain (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p0CCTneN013372; Wed, 12 Jan 2011 07:29:49 -0500 From: Phil Muldoon To: Joel Brobecker Cc: gdb@sourceware.org Subject: Re: runtest gdb testsuite oddities. References: <20110112022548.GB2518@adacore.com> Reply-to: pmuldoon@redhat.com X-URL: http://www.redhat.com Date: Wed, 12 Jan 2011 12:30:00 -0000 In-Reply-To: <20110112022548.GB2518@adacore.com> (Joel Brobecker's message of "Tue, 11 Jan 2011 21:25:48 -0500") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-01/txt/msg00035.txt.bz2 Joel Brobecker writes: >> Toms check-in today regarding the failure in py-infthread.exp had me >> exploring why I did not see it. For some reason when one runs: runtest >> gdb.python/*.exp the testsuite seems to pass just fine. But when one >> runs just one (failing) exp file, the test fails as it should. I'm not >> sure why, and my fu regarding dejagnu is very slim. Can anyone explain >> what is going on here? Hopefully it is something silly I have done. > > Each testcase (.exp) is actually part of the same run. When you think > of scripts being executed, they are actually files being sourced. > So what I am thinking happened to you is that, in your normal context, > you first "ran" (in other words: sourced) a gdb.python testcase that > called "load_lib gdb-python.exp", and thus defined the > gdb_py_test_silent_cmd procedure. "Thanks" to that, by the time dejagnu > "ran" py-infthread.exp, tcl/expect could find gdb_py_test_silent_cmd, > even though the "script" is missing a call to load_lib. It also seems to happen with just a plain old "make check" too (I guess as it equates to runtest $$/*.exp in each directory.) The import being sourced from a previous test unit sounds bogus. (Not that I know how to fix it, or even if we can.) Cheers Phil