Add a new attribute self.lldbHere, representing the fullpath to the 'lldb' executable

built locally from the source tree.  This is distinguished from self.lldbExec, which
can be used by test/benchmarks to measure the performances against other debuggers.

You can use environment variable LLDB_EXEC to specify self.lldbExec to the dotest.py
test driver, otherwise it is going to be populated with self.lldbHere.

Modify the regular tests under test dir, i.e., not test/benchmarks, to use self.lldbHere.
Also modify the benchmarks tests to use self.lldbHere when it needs an 'lldb' executable
with debug info to do the performance measurements.

llvm-svn: 138608

1 files changed, 1 insertions, 1 deletions

diff --git a/lldb/test/functionalities/command_regex/TestCommandRegex.py b/lldb/test/functionalities/command_regex/TestCommandRegex.py
index 27bdd87bc11..a404de19dcc 100644
--- a/lldb/test/functionalities/command_regex/TestCommandRegex.py
+++ b/lldb/test/functionalities/command_regex/TestCommandRegex.py
@@ -18,7 +18,7 @@ class CommandRegexTestCase(TestBase):
         regex_prompt = "Enter regular expressions in the form 's/<regex>/<subst>/' and terminate with an empty line:\r\n"
         regex_prompt1 = "\r\n"
 
-        child = pexpect.spawn('%s' % self.lldbExec)
+        child = pexpect.spawn('%s' % self.lldbHere)
         # Turn on logging for what the child sends back.
         if self.TraceOn():
             child.logfile_read = sys.stdout