[Lldb-commits] [lldb] [lldb][DWARFASTParserClang] Support constant index encoding of DW_AT_object_pointer (PR #144998)

[Michael Buch via lldb-commits]

Michael137 wrote:

> It seems the buildbot [lldb-remote-linux-ubuntu](https://lab.llvm.org/buildbot/#/builders/195/builds/10819) is broken after this patch.
> 
> ```
> Unresolved Tests (3):
>   lldb-api :: commands/expression/import-std-module/basic/TestImportStdModule.py
>   lldb-api :: commands/expression/import-std-module/conflicts/TestStdModuleWithConflicts.py
>   lldb-api :: commands/expression/import-std-module/retry-with-std-module/TestRetryWithStdModule.py
> ```
> 
>  ```
> UNSUPPORTED: LLDB (/home/buildbot/worker/as-builder-9/lldb-remote-linux-ubuntu/build/bin/clang-aarch64) :: test_dsym
> (TestStdModuleWithConflicts.TestImportStdModuleConflicts.test_dsym) 
> (test case does not fall in any category of interest for this run) 
> python3.12: /home/buildbot/worker/as-builder-9/lldb-remote-linux-ubuntu/llvm-project/llvm/../clang/include/clang/AST/Type.h:952: 
> const clang::ExtQualsTypeCommonBase* clang::QualType::getCommonPtr() const: Assertion `!isNull() && "Cannot retrieve a NULL type pointer"' failed.
> PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace.
> Stack dump:
> ...
> ```

Looks like it got resolved? Possibly a different root cause? I think I saw some Modules related changes flying around that could've caused this

https://github.com/llvm/llvm-project/pull/144998