[Lldb-commits] [PATCH] D27291: Handle UTF-16 and UTF-32 constant CFStrings

2016-12-01 Thread Jim Ingham via Phabricator via lldb-commits
jingham accepted this revision. jingham added a comment. This revision is now accepted and ready to land. Looks good. Repository: rL LLVM https://reviews.llvm.org/D27291 ___ lldb-commits mailing list lldb-commits@lists.llvm.org

[Lldb-commits] [PATCH] D27291: Handle UTF-16 and UTF-32 constant CFStrings

2016-12-01 Thread Sean Callanan via Phabricator via lldb-commits
spyffe updated this revision to Diff 79935. spyffe added a comment. Updated to reflect Jim's comments. Repository: rL LLVM https://reviews.llvm.org/D27291 Files: packages/Python/lldbsuite/test/lang/objc/unicode-string/TestUnicodeString.py

[Lldb-commits] [PATCH] D27291: Handle UTF-16 and UTF-32 constant CFStrings

2016-11-30 Thread Jim Ingham via Phabricator via lldb-commits
jingham added a comment. Other than the request for a more logging, this seems fine. Comment at: source/Plugins/ExpressionParser/Clang/IRForTarget.cpp:514-515 + default: + encoding_flags = 0x0600; /* fall back to 0x0600, kCFStringEncodingASCII */ + } + Constant *encoding_arg

[Lldb-commits] [PATCH] D27291: Handle UTF-16 and UTF-32 constant CFStrings

2016-11-30 Thread Sean Callanan via Phabricator via lldb-commits
spyffe created this revision. spyffe added a reviewer: jingham. spyffe added a subscriber: LLDB. spyffe set the repository for this revision to rL LLVM. We have a longstanding issue where the expression parser does not handle wide CFStrings (e.g., `@"凸凹"`) correctly, producing the useless error