Sean Callanan cd1eb72bab Handle UTF-16 and UTF-32 constant CFStrings ... We have a longstanding issue where the expression parser does not handle wide CFStrings (e.g., @"凸凹") correctly, producing the useless error message Internal error [IRForTarget]: An Objective-C constant string's string initializer is not an array error: warning: expression result unused error: The expression could not be prepared to run in the target This is just a side effect of the fact that we don't handle wide string constants when converting these to CFStringCreateWithBytes. That function takes the string's encoding as an argument, so I made it work and added a testcase. https://reviews.llvm.org/D27291 <rdar://problem/13190557> llvm-svn: 288386		2016-12-01 17:46:51 +00:00
..
pre_kill_hook	added Linux support for test timeout sampling	2016-09-26 20:25:47 +00:00
support	*** This commit represents a complete reformatting of the LLDB source code	2016-09-06 20:57:50 +00:00
test	Handle UTF-16 and UTF-32 constant CFStrings	2016-12-01 17:46:51 +00:00
test_event	test infra: clear file-charged issues on rerun of file	2016-10-01 00:17:08 +00:00
__init__.py	*** This commit represents a complete reformatting of the LLDB source code	2016-09-06 20:57:50 +00:00
.clang-format	Updated .clang-format rules so bring LLDB in line with LLVM standards.	2016-09-06 17:19:00 +00:00