llvm-project.git/lldb, branch main

[lldb] [disassembler] chore: update VariableAnnotator::Annotate to except only Instruction as param and drop module and target (#168276)

2025-11-22T16:01:34+00:00

[NFC][lldb] Remove duplicated checks (#169093)

2025-11-22T05:17:52+00:00

Removed duplicated checks reported by cppcheck

[lldb] Remove redundant declarations (NFC) (#169003)

2025-11-22T04:31:54+00:00

In C++17, static constexpr members are implicitly inline, so they no
longer require an out-of-line definition.

Identified with readability-redundant-declaration.

[NFC][LLDB] Make it possible to detect if the compiler used in tests supports -fbounds-safety (#169112)

2025-11-22T03:01:31+00:00

This patch makes it possible to detect in LLDB shell and API tests if
`-fbounds-safety` is supported by the compiler used for testing. The
motivation behind this is to allow upstreaming
https://github.com/swiftlang/llvm-project/pull/11835 but with the tests
disabled in upstream because the full implementation of -fbounds-safety
isn't available in Clang yet.

For shell tests when -fbounds-safety is available the
`clang-bounds-safety` feature is available which means tests can be
annotated with `# REQUIRES: clang-bounds-safety`.

API tests that need -fbounds-safety support in the compiler can use the
new `@skipUnlessBoundsSafety` decorator.

rdar://165225507

Revert "Reland [MS][clang] Add support for vector deleting destructors" (#169116)

2025-11-22T01:14:34+00:00

This reverts 4d10c1165442cbbbc0017b48fcdd7dae1ccf3678 and its two
dependent commits: e6b9805b574bb5c90263ec7fbcb94df76d2807a4 and
c243406a695ca056a07ef4064b0f9feee7685320, see discussion in
https://github.com/llvm/llvm-project/pull/165598#issuecomment-3563825509.

[lldb] Remove Base::unique from NonNullSharedPtr (#169130)

2025-11-22T00:10:06+00:00

It seems like this fails on macOS with C++20

[lldb] Fix EditlineTest closing files multiple times. (#169100)

2025-11-21T23:29:43+00:00

This updates the EditlineTest to use `lldb::FileSP` to ensure the
associated FDs are only closed a single time.

Currently, there is some confusion between the `FilePointer`,
`PseudoTerminal` and `LockableStreamFile` about when the files are
closed resulting in a crash in some due to a `fflush` on a closed file.

[lldb] Restore the old behavior in lua-typemaps.swig (#169103)

2025-11-21T22:13:24+00:00

Restore the original behavior (i.e. before #167764), which uses
eOpenOptionWriteOnly, not eOpenOptionReadWrite. Fixes TestLuaAPI.py.

[lldb] Don't enable the Limited C API with Python 3.13 and SWIG 4.4.0 (#169065)

2025-11-21T17:27:17+00:00

Don't automatically enable the Limited C API when we're targeting Python
3.13 or later in combination with SWIG 4.4.0 due to a bug in the latter.

SWIG Issue: https://github.com/swig/swig/issues/3283
SWIG PR: https://github.com/swig/swig/pull/3285

[lldb] Add MockMemory class for dwarf expression testing (#168467)

2025-11-21T16:44:08+00:00

This change unifies the way that we specify mocked memory to make it
easy to control the process and target memory contents for unit tests.
We add a MockMemory class that can be used in dwarf expression testing
to specify the output of the `ReadMemory` function.

The MockMemory class is built on a map that maps a `(address, size)`
pair to a vector of bytes that is `size` bytes long and contains the
memory contents for that `address`.

The MockProcessWithMemRead and MockTarget classes are updated to use the
new MockMemory interface. The MockProcessWithMemRead class was renamed
to MockProcess and the old MockProcess was deleted. The old MockProcess had
and ReadMemory implementation that returned the value `i & 0xff` for reading the
address `i` and was easily be replaced with the MockMemory object.

The CreateTestContext function now takes optional values for process memory and 
target memory and uses those to create the mock objects.