[Lldb-commits] [PATCH] D62015: Make sure GetObjectDescription falls back to the Objective-C runtime.
Jason Molenda via Phabricator via lldb-commits
lldb-commits at lists.llvm.org
Thu May 16 10:14:21 PDT 2019
jasonmolenda added a comment.
My one concern is how this will work in a swift-lldb where we have a swift ValueObject, the print description fails, and we fall back to the ObjC print description. That's a change in behavior, right? I imagine worst case is that the objc print description will fail to produce anything and we'll have the same behavior as we do today.
================
Comment at: lldb/packages/Python/lldbsuite/test/lang/objcxx/cxx-bridged-po/TestObjCXXBridgedPO.py:16
+ @skipIfWindows
+ @skipIfNetBSD
+ def test_bridged_type_po(self):
----------------
@skipUnlessDarwin
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D62015/new/
https://reviews.llvm.org/D62015
More information about the lldb-commits
mailing list