I'm not actually too sure of the compatibility situation between Python
versions, but I think forcing a user to install a Python 3.5.x version is
quite reasonable for LLDB use.
I can also upstream this if the community is interested.
Ted if you have a patch to fix the scripting feature for LLDB on Windows it
would be much appreciated by me and other Rust developers trying to use
LLDB with Visual Studio Code.
Jamie
On Mon, Jul 3, 2017 at 4:54 AM, Pavel Labath wrote:
> On 30 June 2017 at 21:34, Ted Woodward via lldb-dev
> wrote:
> > I’ve seen crashes on Linux when building with 2.7.6 and using the 2.7.3
> > .so/library directory, so I’m not willing to say building on Windows with
> > 3.6.1 and using the 3.5.2 dll/library directory will work.
> This is a bit problematic setup. I would expect that the opposite
> (building with version X, and running with version Y >= X) will work,
> but using an older runtime version is tricky because your code may end
> using symbols which are not present in the older version.
>
> Without more information, it's hard to say whether this was a problem
> in your case. It could be that python 2.7.3 simply has a bug, and the
> crash would happen even if you were using the same version of python
> for building (our bots are at 2.7.6, and I am not aware of anyone
> testing/using/shipping lldb with an older version of python)
>
> pl
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
