llvm-project.git/lldb/test/Shell/SymbolFile/DWARF, branch main

[lldb][test] Try to fix dwarf64 test on Windows

2025-11-17T10:15:38+00:00

Think it's just a path slash difference.

Fixes #167997.

[lldb] Add the ability to load DWARF64 .debug_str_offsets tables for DWARF32 DWARF units in .dwp files in LLDB. (#167997)

2025-11-15T00:35:43+00:00

This patch is updating the reading capabilities of the LLDB DWARF parser
for a llvm-dwp patch https://github.com/llvm/llvm-project/pull/167457
that will emit .dwp files where the compile units are DWARF32 and the
.debug_str_offsets tables will be emitted as DWARF64 to allow .debug_str
sections that exceed 4GB in size.

[LLDB] Use %clang_host instead of %clang in test (NFC)

2025-11-13T21:00:42+00:00

[NFCI][lldb][test] Fix mismatched C/C++ substitutions (#165773)

2025-10-30T21:18:32+00:00

Most of the cases were where a C++ file was being compiled with the C substitution.
There were a few cases of the opposite though.

LLDB seems to be the only real culprit in the LLVM codebase for these mismatches.
Rest of the LLVM presumably sticks at least language-specific options in the common substitutions
making the mistakes immediately apparent.

I found these by using Clang frontend configuration files containing language-specific options for
both C and C++ (e.g. `-std=c2y` and `-std=c++26`).

[lldb][DWARFASTParserClang] Simplify obsolete error condition for malformed array member type offsets (#160132)

2025-09-29T20:05:37+00:00

First time check was introduced in
`fa3ab4599d717feedbb83e08e7f654913942520b` to work around a debug-info
generation bug in Clang. This bug was fixed in Clang-4. The check has
since been adjusted (first in
`808ff186f6a6ba1fd38cc7e00697cd82f4afe540`, and then most recently in
`370db9c62910195e664e82dde6f0adb3e255a4fd`).

This check is getting quite convoluted, and all it does is turn an
`array[1]` into an `array[0]` type when it is deemed correct. At this
point the workaround probably never fires, apart from actually valid
codegen. This patch removes the special conditions and emits the error
specifically in those cases where we know the DWARF is malformed.

Added some shell tests for the error case.

[lldb][test] Make hex prefix optional in DWARF union types test

2025-09-25T09:23:41+00:00

Fixes #159401

On Windows there is no hex prefix, I suspect because somewhere we
print a pointer. I'd prefer to fix that itself but can't get to
a Windows machine at the moment. It's not important to the purpose
of the test anyway.

Fix a bug where an error was emitted for GCC union types. (#159401)

2025-09-24T23:27:43+00:00

GCC doesn't add DW_AT_data_member_location attributes to the
DW_TAG_member children of DW_TAG_union_type types. An error was being
emitted incorrectly for these cases fr om the DWARFASTParserClang. This
fixes that issue and adds a test.

[LLDB] Fix deterministic-build.cpp post #156931 (#156983)

2025-09-04T23:56:17+00:00

This test was brokem by migrating to the lit internal shell due to a
lack of env prefix for setting environment variables. This was fixed in
prevented the breakpoint in the test from mapping to anything, causing
the test to file. This patch restores the original line numbering.

[LLDB] Fix tests that fail when using internal shell. (#156931)

2025-09-04T17:43:09+00:00

These tests were failing on darwin, because the internal shell needs
environment var definitions to start with 'env'. This PR (hopefully)
fixes that problem.

[LLDB] Make internal shell the default for running LLDB lit tests. (#156729)

2025-09-03T23:34:29+00:00

This patch updates the lld lit test config to use the internal shell by
default. This has some performance advantages (~10-15%) and also
produces nicer failure output. It also updates the two LLDB tests to not
require shell (so that they run under the internal shell), after first
verifying that they run and pass using the internal shell; and it fixes
one test that was not passing under the internal shell.