Re: [lldb-dev] Running a single test

2016-02-09 Thread Ed Maste via lldb-dev
On 9 February 2016 at 17:19, Zachary Turner wrote: > Try passing the directory to start in as the last argument. Also make sure > you include .py on the filename when using -p (I don't actually know if this > is required but I do it). > > % python dotest.py --executable /tank/emaste/src/llvm/buil

Re: [lldb-dev] Running a single test

2016-02-09 Thread Tamas Berghammer via lldb-dev
Zachary's solution will work as well but that one won't make debugging the test too easy (still using several processes). If you want to run just 1 test then you have to specify --no-multiprocess and then you can use the same flags as before (-p, -f) On Tue, Feb 9, 2016 at 10:19 PM Zachary Turner

Re: [lldb-dev] Running a single test

2016-02-09 Thread Zachary Turner via lldb-dev
Try passing the directory to start in as the last argument. Also make sure you include .py on the filename when using -p (I don't actually know if this is required but I do it). % python dotest.py --executable /tank/emaste/src/llvm/build-nodebug/bin/lldb -C /usr/bin/clang -v -t -p TestCppIncomple

[lldb-dev] Running a single test

2016-02-09 Thread Ed Maste via lldb-dev
I've been away from LLDB development for a little while but am starting to work on it again. I used to run a few tests using dotest.py's -f or -p flags, but they don't seem to be working now. -f filterspec Specify a filter, which consists of the test class name,