From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18958 invoked by alias); 12 Jan 2011 02:26:09 -0000 Received: (qmail 18950 invoked by uid 22791); 12 Jan 2011 02:26:08 -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, 12 Jan 2011 02:26:03 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id A7AD32BAB9F; Tue, 11 Jan 2011 21:26:01 -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 J6kGMplI+mYG; Tue, 11 Jan 2011 21:26:01 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id C47A92BAB82; Tue, 11 Jan 2011 21:26:00 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id CC6A21459AD; Tue, 11 Jan 2011 21:25:48 -0500 (EST) Date: Wed, 12 Jan 2011 02:26:00 -0000 From: Joel Brobecker To: Phil Muldoon Cc: gdb@sourceware.org Subject: Re: runtest gdb testsuite oddities. Message-ID: <20110112022548.GB2518@adacore.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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/msg00034.txt.bz2 > 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. -- Joel