diff options
| author | George Rimar <grimar@accesssoftek.com> | 2019-10-22 08:52:45 +0000 |
|---|---|---|
| committer | George Rimar <grimar@accesssoftek.com> | 2019-10-22 08:52:45 +0000 |
| commit | 78d632d1055467dd2880dc9ff6dfdc554505eda7 (patch) | |
| tree | 2fe971d63d55994acba7cc0f25622f3ca6093819 /lldb/packages/Python/lldbsuite/test/commands/command/script/callables.py | |
| parent | ecc999101aadc8dc7d4af9fd88be10fe42674aa0 (diff) | |
| download | bcm5719-llvm-78d632d1055467dd2880dc9ff6dfdc554505eda7.tar.gz bcm5719-llvm-78d632d1055467dd2880dc9ff6dfdc554505eda7.zip | |
[LLVMDebugInfoPDB] - Use cantFail() instead of assert().
Currently injected-sources-native.test fails with "Expected<T>
value was in success state.
(Note: Expected<T> values in success mode must still be checked
prior to being destroyed)"
when llvm is compiled with LLVM_ENABLE_ABI_BREAKING_CHECKS in Release.
The problem is that getStringForID returns Expected<StringRef>
and Expected value must always be checked, even if it is in success state.
Checking with assert only helps in Debug and is wrong.
Differential revision: https://reviews.llvm.org/D69251
llvm-svn: 375492
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/commands/command/script/callables.py')
0 files changed, 0 insertions, 0 deletions
