[Lldb-commits] [PATCH] D94063: lldb: Add support for DW_AT_ranges on DW_TAG_subprograms

Tue Jan 12 15:29:01 PST 2021

dblaikie added a comment.

In D94063#2492450 <https://reviews.llvm.org/D94063#2492450>, @DavidSpickett wrote:

> Do you have python enabled in the build? (https://lldb.llvm.org/resources/build.html#preliminaries)
>
> The cmake option LLDB_ENABLE_PYTHON defaults to Auto which has tripped me up in the past. If you set it to YES then you'll get a build error if it fails to find a suitable Python instead of silently disabling it.

Thanks for the hint! Yep, seems I didn't have the python3-dev package installed (took a while to stare at the error messages to guess/understand that that's what I was missing)

That got a few of these tests running, but still a significant chunk are "unsupported" due to (well, at least some are due to this - I'm guessing quite a few are due to this):

  lldb version 12.0.0 (git at github.com:llvm/llvm-project.git revision d49974f9c98ebce5a679eced9f27add138b881fa)
    clang revision d49974f9c98ebce5a679eced9f27add138b881fa
    llvm revision d49974f9c98ebce5a679eced9f27add138b881fa
  Libc++ tests will not be run because: Compiling with -stdlib=libc++ fails with the error: <stdin>:1:10: fatal error: 'algorithm' file not found
  #include <algorithm>
           ^~~~~~~~~~~
  1 error generated.

  Skipping following debug info categories: ['dsym', 'gmodules']

But I do have libc++ and libc++abi listed as projects to build in my cmake config - but I guess because the just-built clang and just-built libc++ aren't installed, clang can't find libc++ so these tests fail/get marked as unsupported.

But how do these tests work for other people? Do they ever run in a plain build like this? It seems like they should/that would be important.

Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D94063/new/

https://reviews.llvm.org/D94063