Jim Ingham e8a2fd5e7b An SBValue whose underlying ValueObject has no valid value, but does ...

hold an error should:

(a) return false for IsValid, since that's the current behavior and is
    a convenient way to check "should I get the value for this".
(b) preserve the error when an SBValue is made from it, and print the
    error in the ValueObjectPrinter.

Make that happen.

Differential Revision: https://reviews.llvm.org/D144664

2023-02-28 16:41:20 -08:00

..

CMakeLists.txt

…

CXXFunctionPointer.cpp

…

DataVisualization.cpp

[lldb] Add matching based on Python callbacks for data formatters.

2022-10-19 12:53:38 -07:00

DumpValueObjectOptions.cpp

…

FormatCache.cpp

…

FormatClasses.cpp

…

FormatManager.cpp

[lldb] Add matching based on Python callbacks for data formatters.

2022-10-19 12:53:38 -07:00

FormattersHelpers.cpp

[NFCI] More TypeCategoryImpl refactoring.

2022-10-10 15:14:55 -07:00

LanguageCategory.cpp

…

StringPrinter.cpp

…

TypeCategory.cpp

[lldb] Add matching based on Python callbacks for data formatters.

2022-10-19 12:53:38 -07:00

TypeCategoryMap.cpp

[lldb] Add matching based on Python callbacks for data formatters.

2022-10-19 12:53:38 -07:00

TypeFormat.cpp

[lldb] Use std::optional instead of llvm::Optional (NFC)

2023-01-07 14:18:35 -08:00

TypeSummary.cpp

…

TypeSynthetic.cpp

…

ValueObjectPrinter.cpp

An SBValue whose underlying ValueObject has no valid value, but does

2023-02-28 16:41:20 -08:00

VectorType.cpp

[lldb] Use std::optional instead of llvm::Optional (NFC)

2023-01-07 14:18:35 -08:00