On 21/02/2020 23:32, Ted Woodward via lldb-dev wrote:
> Looking into differences, I’m using swig 3.0.12 and the bot is using
> swig 3.0.2. I’m building with 3.0.2 on my machine right now, but it will
> take a while to finish!
I think this could very likely be the cause. We use a different
I believe there are more than 1 python install on the machines, but we set the
PYTHON_HOME cmake variable to get it to use the Python we want. Both copies
spit out 3.5.1 when I print sys.version (but both are using the same
python35.dll).
Both machines are 64 bit; I’m launching lldb from both
Just guessing: Does either machine have more than one Python installation?
Windows Server is, by default, more locked down than the standard editions,
which can affect the search path. Perhaps you're not getting the Python
you think you're getting on one of the machines.
Are both machines
I first noticed this issue when running
print(lldb.SBHostOS.GetLLDBPythonPath()) in the script interpreter. It worked
as expected on Linux and with an LLDB that I built on my machine, but when I
ran it in an LLDB that our buildbots built, I got the wrong value -
