From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22538 invoked by alias); 24 Feb 2004 23:27:39 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 22529 invoked from network); 24 Feb 2004 23:27:38 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 24 Feb 2004 23:27:38 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1Avlxi-0007XN-Do for ; Tue, 24 Feb 2004 18:27:38 -0500 Date: Tue, 24 Feb 2004 23:27:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Re: -file-list-exec-source-files testcase Message-ID: <20040224232738.GA26943@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com References: <20040224172218.GA18323@white> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040224172218.GA18323@white> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-02/txt/msg00346.txt.bz2 On Tue, Feb 24, 2004 at 12:22:18PM -0500, Bob Rossi wrote: > Hi, > > I was wondering, the testcase I am writing for > -file-list-exec-source-files has output like > > (gdb) > -file-list-exec-source-files > ^done,files=[ > {filename="/build/buildd/glibc-2.3.2.ds1/build-tree/i386-libc/csu/crtn.S"}, > {filename="/build/buildd/glibc-2.3.2.ds1/build-tree/i386-libc/csu/crti.S"}, > {filename="init.c"}, > {filename="../sysdeps/i386/elf/start.S"}, > {filename="./gdb.mi/basics.c",fullname="/home/bob/cvs/src/src/src/gdb/testsuite/gdb.mi/basics.c"} > ] > (gdb) > > > There are no line breaks in the real output, that is for convenience above. > > So, I was wondering, the output of the MI command looks like > {filename=.*}+ or {filename=.*,fullname=/.*}+ > where you can have 0 or more filename or filename/fullname pairs. Since I > am testing the program 'basics' should I just test the literal output of > this command when run against basics, or should I make it general so > that it should work for any output of -file-list-exec-source-files? You probably want to match any additional entries before or after the one for basics.c, and make sure that basics.c is listed. Something like: ({filename="\[^"\]*"(,{fullname="\[^"\]*"})?,)* ({filename="\[^"\]*/basics.c"(,{fullname="/\[^"\]*/basics.c"})?,)* ({filename="\[^"\]*"(,{fullname="\[^"\]*"})?,)* I'm not sure if the leading / is OK. Probably you'll need to accept some sort of drive prefix for one of the DOS/Windows based environments too... -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer