Hello everyone,
We're getting closer to the final release, and as usual I'd like to
ask you all to help writing release notes.
When the release happens, the first thing people tend to look at are
the release notes, so they're a great opportunity to highlight the
work that's been done over the pas
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 -
/lib/site-packages/lib/site-pack
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 64-bi
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 a
