llvm-project.git/lldb/source/ValueObject/ValueObjectDynamicValue.cpp, branch users/nico/python-2

[lldb] Upgrade CompilerType::GetBitSize to return llvm::Expected (#129601)

2025-03-05T18:21:19+00:00

This patch pushes the error handling boundary for the GetBitSize()
methods from Runtime into the Type and CompilerType APIs. This makes it
easier to diagnose problems thanks to more meaningful error messages
being available. GetBitSize() is often the first thing LLDB asks about a
type, so this method is particularly important for a better user
experience.

rdar://145667239

[lldb][NFC] Replace GetLocalBufferSize() with GetLocalBuffer() (#126333)

2025-02-08T03:12:35+00:00

[lldb] Make ValueObjectDynamicValue::UpdateValue() point to a host b… (#125143)

2025-02-07T03:04:01+00:00

…uffer

ValueObjectDynamicValue::UpdateValue() assumes that the dynamic type
found by GetDynamicTypeAndAddress() would return an address in the
inferior. This commit makes it so it can deal with being passed a host
address instead.

This is needed downstream by the Swift fork.

rdar://143357274

[lldb] Move ValueObject into its own library (NFC) (#113393)

2024-10-25T03:20:48+00:00

ValueObject is part of lldbCore for historical reasons, but conceptually
it deserves to be its own library. This does introduce a (link-time) circular
dependency between lldbCore and lldbValueObject, which is unfortunate
but probably unavoidable because so many things in LLDB rely on
ValueObject. We already have cycles and these libraries are never built
as dylibs so while this doesn't improve the situation, it also doesn't
make things worse.

The header includes were updated with the following command:

```
find . -type f -exec sed -i.bak "s%include \"lldb/Core/ValueObject%include \"lldb/ValueObject/ValueObject%" '{}' \;
```