Re: [lldb-dev] [9.0.0 Release] Release schedule

[Hans Wennborg via lldb-dev]

On Wed, Jun 19, 2019 at 10:19 AM Hans Wennborg  wrote:
>
> Hello everyone,
>
> Even though 8.0.1 isn't quite out the door yet, it's time to start
> planning for the next major release, 9.0.0.
>
> This is my proposed schedule:
>
> - 18 July 2019: Branch, rc1 soon after
> - 7 August: rc2
> - 28 August: final (not slipping past first half of September).
>
> Please let me know what you think.

The schedule is now on the llvm.org web site.

Thanks,
Hans
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Swig/Python version incompatibility

[Adrian McCarthy via lldb-dev]

tl;dr:  To avoid a compatibility problem with Swig, don't upgrade to Python
3.7.

While chasing down the cause of lots of lldb test failures on Windows, I
discovered that there's a compatibility bug with Python 3.7 and Swig 3.0.12.

Python 3.7 tighted up the tp_new API, which SWIG generates calls to.
Specifically, you can see assertion failures for "PyTuple_Check(args)" for
pretty much any invocation of the SBAPI.  (This appears only if you're
using a debug version of Python, because the assertion is in the Python
implementation.)

Swig 4.0 has a fix to satisfy Python's tighter expectation, so I upgraded
to Swig 4.0, but then other problems surfaced (like undefined references to
__swig_getmethods__).

Some context:  https://github.com/swig/swig/issues/1321

So, for now, it looks like we have to stick with Python 3.6/Swig 3.0.12.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] Trouble running Python tests on Windows

[Adrian McCarthy via lldb-dev]

I can confirm that there are problems building with Swig 4.

I've also just found that there's a bug in versions of Swig before 4 that
makes the code it generates incompatible with Python 3.7.  (See lldb-dev@
for a message I just sent out about this.)

Python 3.6 with Swig 3.0.12 is working well for me on Windows.

On Fri, May 31, 2019 at 9:15 AM Ted Woodward via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> Run the cmake gui, and point it to the correct source and build
> directories. Look for key “SWIG_EXECUTABLE”. If it doesn’t exist, set it to
> your swig exe. Mine is C:/swigwin-3.0.12/swig.exe , for example. If you
> change it, hit the configure and then generate buttons, then rebuild and
> rerun the tests.
>
>
>
> I haven’t built with swig 4, just swig 3. I’ll let someone else answer if
> swig 4 works!
>
>
>
> *From:* lldb-dev  *On Behalf Of *Alexandre
> Ganea via lldb-dev
> *Sent:* Friday, May 31, 2019 10:42 AM
> *To:* lldb-dev@lists.llvm.org
> *Subject:* [EXT] [lldb-dev] Trouble running Python tests on Windows
>
>
>
> Hi,
>
>
>
> I can’t seem to run the lldb python tests on my Windows 10 setup. I use
> the following cmd-line to generate:
>
>
>
> cmake -G Ninja f:/svn/llvm -DCMAKE_BUILD_TYPE=Release
> -DLLVM_OPTIMIZED_TABLEGEN=true -DLLVM_EXTERNAL_LLD_SOURCE_DIR=f:/svn/lld
> -DLLVM_EXTERNAL_CLANG_SOURCE_DIR=f:/svn/clang -DLLVM_TOOL_LLD_BUILD=true
> -DLLVM_TOOL_CLANG_BUILD=true -DLLVM_ENABLE_PDB=true
> -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_EXTERNAL_LLDB_SOURCE_DIR=f:/svn/lldb
> -DLLVM_TOOL_LLDB_BUILD=true
> -DPYTHON_HOME="C:\Users\aganea\AppData\Local\Programs\Python\Python37"
>
>
>
> Followed by: ninja check-all, which ends up in a bunch of:
>
>
>
>  TEST 'lldb-Suite ::
> tools/lldb-server/TestAppleSimulatorOSType.py' FAILED 
>
> Unable to find 'RESULT: PASSED' in dotest output:
>
>
>
> lldb version 9.0.0 (https://aga...@llvm.org/svn/llvm-project/lldb/trunk
> revision 361826)
>
>   clang revision 361826
>
>   llvm revision 361826
>
> LLDB library dir: F:\svn\buildninja\bin
>
> LLDB import library dir: F:\svn\buildninja\bin\..\lib
>
> Traceback (most recent call last):
>
>   File "F:/svn/lldb/test/dotest.py", line 7, in 
>
> lldbsuite.test.run_suite()
>
>   File "F:\svn\lldb\packages\Python\lldbsuite\test\dotest.py", line 1243,
> in run_suite
>
> import lldb
>
>   File "F:\svn\buildninja\lib\site-packages\lldb\__init__.py", line 1500,
> in 
>
> class SBAddress(object):
>
>   File "F:\svn\buildninja\lib\site-packages\lldb\__init__.py", line 1675,
> in SBAddress
>
> __swig_getmethods__["module"] = GetModule
>
> NameError: name '__swig_getmethods__' is not defined
>
>
>
> Swig 4.0.0 is there in %PATH%. I’m using MSVC 19.16.27031.1 for compiling.
> I’ve tried with Clang 8.0, same issues.
>
> Any idea on what could be missing?
>
>
>
> Thanks in advance!
>
> Alex.
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] "error: summary string parsing error" on Fedora 30

[Bob Eastbrook via lldb-dev]

With Clang 8.0.0 and libstd++ 9.1.1 on Fedora 30 x86_64, I get this
error from LLDB when trying to see the value of a string:

"error: summary string parsing error"

The code is simply:

std::string msg{"foo bar baz"};

With libcxx 8.0.0, instead of the above error, I simply see "??" when
inspecting the msg variable.

All of the above works fine for me in Ubuntu 19.04. I only have the
problem with Fedora 30.  Tried in both CLion and VS Code.

How should I troubleshoot this?  Could I be missing a package?
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev