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 LLD
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 se
Note that building with 3.6.x and using 3.5.x won't work, but any of 3.5.x
revisions should be compatible between themselves.
On Fri, Jun 30, 2017 at 1:41 PM, Zachary Turner via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
>
>
> On Fri, Jun 30, 2017 at 1:34 PM Ted Woodward
> wrote:
>
>> I’ve seen
On Fri, Jun 30, 2017 at 1:34 PM Ted Woodward
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. Python has never
> been very forgi
Aurora Forum, a Linux
Foundation Collaborative Project
From: Zachary Turner [mailto:ztur...@google.com]
Sent: Friday, June 30, 2017 3:05 PM
To: Ted Woodward ; Jamie Madill
; lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] Python scripting in Windows LLDB
On Fri, Jun 30, 2017 at 12:39 PM
On Fri, Jun 30, 2017 at 12:39 PM Ted Woodward via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Python support on Windows is much more problematic than support on
> something like MacOS or Linux. The python you use when you run lldb must be
> the same python used when you build it. Bad things happe
Foundation Collaborative Project
From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Jamie
Madill via lldb-dev
Sent: Thursday, June 29, 2017 10:30 AM
To: lldb-dev@lists.llvm.org
Subject: [lldb-dev] Python scripting in Windows LLDB
A ping for this regression - Ted Woodward seems t
A ping for this regression - Ted Woodward seems to have had a patch for
fixing broken Windows scripting support but the 5.0.0 snapshot release
didn't have the fix. Is it possible to land that patch for the next
snapshot?
This is currently breaking LLDB Visual Studio Code integration on Windows
(fo
Zachary Turner ; Vadim Chugunov
>> ; Hans Wennborg ; LLDB > d...@lists.llvm.org>
>> Subject: Re: [lldb-dev] Python scripting in Windows LLDB
>>
>> This may cause some issues with the multi-configuration generators.
>> E.g. a single VS build will create both debug a
t; ; Hans Wennborg ; LLDB d...@lists.llvm.org>
> Subject: Re: [lldb-dev] Python scripting in Windows LLDB
>
> This may cause some issues with the multi-configuration generators.
> E.g. a single VS build will create both debug and release configurations. I
> suspect this is the r
I can push this change upstream if you’d like, Zach.
>
>
>
> --
>
> Qualcomm Innovation Center, Inc.
>
> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
>
>
>
> From: lldb-dev [mailto:lldb-dev-bo
t;
> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
>
>
>
> From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Zachary
> Turner via lldb-dev
> Sent: Friday, May 19, 2017 3:18 PM
> To: Vadim
o: Vadim Chugunov ; Hans Wennborg ; LLDB
Subject: Re: [lldb-dev] Python scripting in Windows LLDB
Hmm, I believe it's only supposed to do that if you're doing a debug build. It
should only require the Python libraries that match your current build. Is it
not doing this?
On Fri, M
Yes, my machine doesn't have the _d.dll files.
On Fri, May 19, 2017 at 1:14 PM, Vadim Chugunov wrote:
> Update: looks like Python detection in CMake now requires debug binaries to
> be there as well (e.g. python35_d.dll), otherwise Python support gets
> disabled. I am wondering if Python the bui
Hmm, I believe it's only supposed to do that if you're doing a debug
build. It should only require the Python libraries that match your current
build. Is it not doing this?
On Fri, May 19, 2017 at 1:15 PM Vadim Chugunov via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Update: looks like Python
Update: looks like Python detection in CMake now requires debug binaries to
be there as well (e.g. python35_d.dll), otherwise Python support gets
disabled. I am wondering if Python the build machine was installed without
the debug stuff.
On Fri, May 19, 2017 at 10:52 AM, Vadim Chugunov wrote:
>
Hi!
I've just noticed that LLDB from the most recent LLVM Windows snapshot
build has Python scripting disabled.
Was this done on purpose and for what reason if so?
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/li
17 matches
Mail list logo
