Re: -file-list-exec-source-files testcase

[Daniel Jacobowitz <drow@false.org>]

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