History log of /llvm-project/lldb/source/ValueObject/ValueObject.cpp (Results 1 – 4 of 4)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: llvmorg-21-init, llvmorg-19.1.7, llvmorg-19.1.6
# ba43a102 04-Dec-2024 cmtice <cmtice@google.com>

[LLDB] Fix error returns in CastToBasicType and CastToEnumType in ValueObject. (#117401)

Update the error returns in ValueObject::CastToBasicType and
ValueObject::CastToEnumType to create new error

[LLDB] Fix error returns in CastToBasicType and CastToEnumType in ValueObject. (#117401)

Update the error returns in ValueObject::CastToBasicType and
ValueObject::CastToEnumType to create new errors and return a
ValueObjectConstResult with the error, rather tnan updating the error in
(and returning) the input ValueObject.

show more ...


Revision tags: llvmorg-19.1.5, llvmorg-19.1.4
# 4714215e 13-Nov-2024 Jonas Devlieghere <jonas@devlieghere.com>

[lldb] Support true/false in ValueObject::SetValueFromCString (#115780)

Support "true" and "false" (and "YES" and "NO" in Objective-C) in
ValueObject::SetValueFromCString.

Fixes #112597


# 1a684591 05-Nov-2024 Pavel Labath <pavel@labath.sk>

Revert "Fix pointer to reference type (#113596)" (#114831)

This reverts commit 25909b811a7ddc983d042b15cb54ec271a673d63 due to
unresolved questions about the behavior of "frame var" and ValueObject

Revert "Fix pointer to reference type (#113596)" (#114831)

This reverts commit 25909b811a7ddc983d042b15cb54ec271a673d63 due to
unresolved questions about the behavior of "frame var" and ValueObject
in the presence of references (see the original patch for discussion).

show more ...


Revision tags: llvmorg-19.1.3
# b852fb1e 25-Oct-2024 Jonas Devlieghere <jonas@devlieghere.com>

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

ValueObject is part of lldbCore for historical reasons, but conceptually
it deserves to be its own library. This does introduce a (link-

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

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%" '{}' \;
```

show more ...