Hi Gábor,
sorry for the late reply, I have been OOO. Thanks for the detailed
report. I think the fact that we load the system lldb from the unit
tests should be considered a bug. I am going to try to find some time
fix this issue.
thanks,
pl
On Fri, 29 Jun 2018 at 15:35, Gábor Márton wrote:
>
>
So, on Ubuntu "sudo apt-get remove python-lldb-4.0" solved this issue.
Thanks again for the guidance.
Cheers,
Gabor
On Fri, Jun 29, 2018 at 4:10 PM Gábor Márton wrote:
> I did a search for the "HLOp" symbol and it turned out it is only used by
> the "LLVMSupport.so" lib.
> So, this did not help
I did a search for the "HLOp" symbol and it turned out it is only used by
the "LLVMSupport.so" lib.
So, this did not help, thus I dug deeper and examined the test binary
further.
`_exit` is called during the initialization of the static HLOp object
(dlopen() calls call_init() which executes the st
Hi Gábor,
thanks for sending me that link line. Unfortunately, I don't see
anything immediately obvious there. (I was expecting there would be
something pulling in LLVMSupport twice, but I don't see anything like
that there).
To fix this, we need to figure out where is the second definition of
th
Hi Pavel,
Thank you for the fix and for taking care of this!
So, the particular test binary is: ScriptInterpreterPythonTests .
And here is the link command:
) ninja ScriptInterpreterPythonTests -v
[1/1] : && /usr/lib/ccache/clang++ -fPIC -fvisibility-inlines-hidden
-Werror=date-time -std=c++11 -W
The core file tests should be fixed as of r335859. I tried reproing
the python unit tests problem, but I couldn't get it to fail that way.
I can help you get to the bottom of it if you're interested, but it's
going to take some interactive debugging (for start I'd need to see
the link command for t
The BUILD_SHARED_LIBS part is likely to be the issue. LLDB libraries
have cyclic dependencies, which don't play well with shared libraries.
I think somebody "fixed" it some time ago (i.e., just made the flag be
ignored for lldb), but I'm not sure if he also checked the unit tests.
I'll see if I can
Hi Pavel,
I do an in-tree build, so lldb is next to clang.
And I use ccache, could that be a problem? If yes then why just with the
unit tests?
Here is how I configured cmake:
cmake ../../git/llvm -G Ninja -DCMAKE_EXPORT_COMPILE_COMMANDS=1
-DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_COMPILER=clang++
-D
Hello Gabor,
The error message (Option 'help-list' registered more than once) leads
me to believe that this is caused by an uncommon (for lldb, at least)
build configuration. Can you share your cmake configuration?
I suspect TestLinuxCore is also failing due to unexpected build
configuration, spe
Hi
By using "ninja check-lldb-unit" some of the unit tests fail with the tip
of the master. (I am using Ubuntu Linux.) The error is always related to
the CommandLine options:
FAIL: lldb-Unit ::
ScriptInterpreter/Python/./ScriptInterpreterPythonTests/PythonDataObjectsTest.TestBorrowedReferences
(1
10 matches
Mail list logo
