Synthetic values are now automatically enabled and active by default. SBValue is set up to always wrap a synthetic value when one is available.

A new setting enable-synthetic-value is provided on the target to disable this behavior.
There also is a new GetNonSyntheticValue() API call on SBValue to go back from synthetic to non-synthetic. There is no call to go from non-synthetic to synthetic.
The test suite has been changed accordingly.
Fallout from changes to type searching: an hack has to be played to make it possible to use maps that contain std::string due to the special name replacement operated by clang
Fixing a test case that was using libstdcpp instead of libc++ - caught as a consequence of said changes to type searching

llvm-svn: 153495

lldb/test/python_api/formatters/main.cpp

@@ -1,4 +1,5 @@
 #include <stdio.h>
+#include <vector>
 
 struct JustAStruct
 {
@@ -34,5 +35,6 @@ int main(int argc, char const *argv[]) {
 	bar.D = 6.28;
 	bar.E = 3100419850;
 	JustAStruct* foo_ptr = &foo;
+	std::vector<int> int_vector;
 	return 0; // Set break point at this line.
 }