https://bugs.llvm.org/show_bug.cgi?id=32920
Tatyana Krasnukha changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|lldb-dev@lists.
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
FYI, The llvm.org server will be down May 20th from 7AM CDT to 1PM CDT. SVN and
llvm.org webpages will be unavailable. Please note that some websites and
services (Mailing lists, Clang and other sub-projects, APT, releases, Bugzilla)
are hosted by other servers and are not impacted.
I apologiz
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:
>
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
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
LLDBConfig.cmake has this:
if (NOT (PYTHON_DEBUG_EXE AND PYTHON_RELEASE_EXE AND PYTHON_DEBUG_LIB AND
PYTHON_RELEASE_LIB AND PYTHON_DEBUG_DLL AND PYTHON_RELEASE_DLL))
message("Python installation is corrupt. Python support will be disabled
for this build.")
set(LLDB_DISABLE_PYTHON
I adapted the AppleObjcTrampolineHandler to my runtime. It works in as
much as that the debugger steps over my intermediate C functions and
breaks in the targetted method.
Unfortunately when I step out of the method, I am not back at the ObjC
call (0x00010ebf) but instead in my intermediat
It would be better if the build fails hard if some dependency isn't
available. I'll never notice a message about Python support being
disabled since there's so much noise in the build anyway.
On Fri, May 19, 2017 at 1:42 PM, Ted Woodward
wrote:
> LLDBConfig.cmake has this:
>
>
>
> if (NOT (PYTH
This is really an orthogonal problem to the thread plans. They are about
answering the question "how do I get from A to B?". But you want to get the
right answer to "If I land in B, do I want to stop there?" This sort of
question is answered with the "ShouldStopHere" mechanism (see
source/Ta
Hi Jim,
Thanks! I didn't know about ThreadPlanShouldStopHere. And your
swift-lldb code does exactly, what I am looking for.
Ciao
Nat!
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
11 matches
Mail list logo
