On Tue, Aug 2, 2011 at 2:07 AM, Phil Muldoon wrote: > Matt Rice writes: > >> On Mon, Aug 1, 2011 at 7:13 AM, Phil Muldoon wrote: > >> Think it was the quoting of $gdb_prompt which had me foiled. >> >> 2011-08-01  Matt Rice   >> >>         * gdb.python/py-prompt.exp: New file. > > Thanks. > >> +++ b/gdb/testsuite/gdb.python/py-prompt.exp >> @@ -0,0 +1,60 @@ >> +# Copyright (C) 2009, 2010, 2011 Free Software Foundation, Inc. >> + > > This is a new file, so we just need 2011. Oops, > Also, the other prompt tests are in python.exp, so this standalone test > is kind of an anomaly.  What do you think about combining the python.exp > prompt tests into this test file?  If you think that is ok, then you can > just submit another consolidation patch after this one has been approved > and checked in. sure don't mind at all, with all the gdb invocations and global variables in this test and python.exp being shared between many tests I didn't want to ugly it up. > If there is a method to utilise a formal PASS/FAIL into the test I would > prefer that. I managed to finagle this into working with a modified gdb_start. I stuck it in lib because i imagine it has to be for the baseboard override to work, even though its only used by this test?