summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/commands/expression/context-object-objc/TestContextObjectObjc.py
diff options
context:
space:
mode:
authorDimitry Andric <dimitry@andric.com>2019-10-10 20:26:59 +0000
committerDimitry Andric <dimitry@andric.com>2019-10-10 20:26:59 +0000
commita42942e0ecd69d14f80aa285112a843692ca1916 (patch)
treec6ddf8ae0fa5ee7a702ca66dfec708d2d2a1da26 /lldb/packages/Python/lldbsuite/test/commands/expression/context-object-objc/TestContextObjectObjc.py
parent79f243296654fa6089b4529219245fe00f372e5a (diff)
downloadbcm5719-llvm-a42942e0ecd69d14f80aa285112a843692ca1916.tar.gz
bcm5719-llvm-a42942e0ecd69d14f80aa285112a843692ca1916.zip
Fix process launch failure on FreeBSD after r365761
Summary: After rLLDB365761, and with `LLVM_ENABLE_ABI_BREAKING_CHECKS` enabled, launching any process on FreeBSD crashes lldb with: ``` Expected<T> must be checked before access or destruction. Expected<T> value was in success state. (Note: Expected<T> values in success mode must still be checked prior to being destroyed). ``` This is because `m_operation_thread` and `m_monitor_thread` were wrapped in `llvm::Expected<>`, but this requires the objects to be correctly initialized before accessing them. To fix the crashes, use `llvm::Optional<>` for the members (as indicated by labath), and use local variables to store the return values of `LaunchThread` and `StartMonitoringChildProcess`. Then, only assign to the member variables after checking if the return values indicated success. Reviewers: devnexen, emaste, MaskRay, mgorny Reviewed By: devnexen Subscribers: jfb, labath, krytarowski, lldb-commits Differential Revision: https://reviews.llvm.org/D68723 llvm-svn: 374444
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/commands/expression/context-object-objc/TestContextObjectObjc.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud