From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29004 invoked by alias); 5 Oct 2006 19:49:24 -0000 Received: (qmail 28993 invoked by uid 22791); 5 Oct 2006 19:49:24 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 05 Oct 2006 19:49:20 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1GVZDa-0002i8-Lc for gdb-patches@sourceware.org; Thu, 05 Oct 2006 15:49:18 -0400 Date: Thu, 05 Oct 2006 19:49:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sourceware.org Subject: Re: [RFA/testsuite] New testcase for set/unset/show substitute-path Message-ID: <20061005194918.GB10269@nevyn.them.org> Mail-Followup-To: gdb-patches@sourceware.org References: <20060808230045.GF19846@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060808230045.GF19846@adacore.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00032.txt.bz2 On Tue, Aug 08, 2006 at 04:00:45PM -0700, Joel Brobecker wrote: > Hello, > > Here is a first try at implementing a testcase for the new > substitute-path commands. I'm only testing the manipulation > of the list of substitution rules at this point, because I still > don't see how to implement something that would test the actual > substitution and work in all cases. I figured this is better than > nothing for now. Mark's already approved this - I definitely agree that some tests are better than no tests :-) As for functionality testing, I would recommend doing it like this. There's already some samples of creating files and directories during testing (e.g. corefile.exp, commands.exp). Use that to make two directories. Put a source file with different contents in each but the same basename. Compile and debug one of them without issuing a "dir" command, unlike most of the existing tests, and verify that we find the file we expect. Then, use "info source" and look for "Compilation directory"; and that should be all you need to use substitute-path to point at the other directory, and verify that now list shows the second file. Sound reasonable? No rush - just offering the suggestion. -- Daniel Jacobowitz CodeSourcery