[Lldb-commits] [PATCH] D39283: [lldb-dev] Update LLDB test cases for 'inlineStepping'
Carlos Alberto Enciso via Phabricator via lldb-commits
lldb-commits at lists.llvm.org
Thu Jan 4 01:00:11 PST 2018
CarlosAlbertoEnciso added a comment.
I have some issues running the LLDB Test Suite in 32-bit and 64-bit mode.
>From the LLDB documentation:
https://lldb.llvm.org/test.html
It is possible to customize the architecture of the test binaries and compiler used by appending -A and -C options respectively to the CMake variable LLDB_TEST_USER_ARGS. For example, to test LLDB against 32-bit binaries built with a custom version of clang, do:
> cmake -DLLDB_TEST_USER_ARGS="-A i386 -C /path/to/custom/clang" -G Ninja
> ninja check-lldb
Doing
> cmake -DLLDB_TEST_USER_ARGS="-A i386" -G Ninja
> ninja check-lldb
or
> cmake -DLLDB_TEST_USER_ARGS="-A x86_64" -G Ninja
> ninja check-lldb
The LLDB Test Suite generates about 1538 errors related to missing cmake targets.
But if I used the CMake variable LLDB_TEST_ARCH as
> cmake -DLLDB_TEST_ARCH="-A i386" -G Ninja
> ninja check-lldb
or
> cmake -DLLDB_TEST_ARCH="-A x86_64" -G Ninja
> ninja check-lldb
The LLDB Test Suite pass.
My questions:
- Am I misunderstanding the use of those CMake variables?
- Does the LLDB Test Suite incorrectly handling those variables?
Thanks
https://reviews.llvm.org/D39283
More information about the lldb-commits
mailing list