| .. |
|
CF.cpp
|
Rename eExecution*** to eExpression*** to be consistent with the result type.
|
2014-05-05 02:47:44 +00:00 |
|
CMakeLists.txt
|
Add TypeValidator.cpp to cmake build.
|
2014-09-05 21:23:09 +00:00 |
|
CXXFormatterFunctions.cpp
|
Improve the way the ObjC data formatters fetch a valid frame to use for running expressions against
|
2014-07-30 21:07:50 +00:00 |
|
Cocoa.cpp
|
<rdar://problem/16540961>
|
2014-04-10 18:17:30 +00:00 |
|
DataVisualization.cpp
|
Introduce the notion of a "type validator" formatter
|
2014-09-05 20:45:07 +00:00 |
|
FormatCache.cpp
|
Introduce the notion of a "type validator" formatter
|
2014-09-05 20:45:07 +00:00 |
|
FormatClasses.cpp
|
<rdar://problem/15530080>
|
2013-11-22 00:02:13 +00:00 |
|
FormatManager.cpp
|
When deciding if one-liner printing applies, and you find a summary, the summary is a good candidate to ask. While in theory one could want one-liner printing with a non-one-liner summary, I don't see LLDB as the best place to solve such inner conflicts
|
2014-09-11 23:00:27 +00:00 |
|
LibCxx.cpp
|
<rdar://problem/16424592>
|
2014-03-31 23:02:25 +00:00 |
|
LibCxxList.cpp
|
Fix Windows build using portable types for formatting the log outputs
|
2014-03-03 15:39:47 +00:00 |
|
LibCxxMap.cpp
|
Recent builds of libcxx actually wrap an std::map's children values in a union containing either a member named __cc, or either of __cc and __nc (const vs. non-const). This level of wrapping is quite useless for LLDB to show to people, so try to detect it, and filter it out
|
2014-09-12 00:55:37 +00:00 |
|
LibCxxUnorderedMap.cpp
|
Fix Windows build using portable types for formatting the log outputs
|
2014-03-03 15:39:47 +00:00 |
|
LibStdcpp.cpp
|
Fix Windows build using portable types for formatting the log outputs
|
2014-03-03 15:39:47 +00:00 |
|
Makefile
|
Only enable RTTI for cxa_demangle.cpp
|
2013-02-15 02:36:40 +00:00 |
|
NSArray.cpp
|
Initial merge of some of the iOS 8 / Mac OS X Yosemite specific
|
2014-06-13 02:37:02 +00:00 |
|
NSDictionary.cpp
|
Improve the way the ObjC data formatters fetch a valid frame to use for running expressions against
|
2014-07-30 21:07:50 +00:00 |
|
NSSet.cpp
|
Fix Windows build using portable types for formatting the log outputs
|
2014-03-03 15:39:47 +00:00 |
|
TypeCategory.cpp
|
Introduce the notion of a "type validator" formatter
|
2014-09-05 20:45:07 +00:00 |
|
TypeCategoryMap.cpp
|
Introduce the notion of a "type validator" formatter
|
2014-09-05 20:45:07 +00:00 |
|
TypeFormat.cpp
|
Fixes for broken Debian build - g++ 4.7 support.
|
2014-07-10 04:39:13 +00:00 |
|
TypeSummary.cpp
|
Allow summary formatters to take ValueObjects into account when deciding whether values/children should be printed and if child names should be shown
|
2014-04-23 23:16:25 +00:00 |
|
TypeSynthetic.cpp
|
TypeSynthetic: Fix a pointer-to-function to void-pointer cast
|
2014-07-22 20:40:01 +00:00 |
|
TypeValidator.cpp
|
Fix the ctor ivar initialization formatting for Debugger,
|
2014-09-12 01:50:46 +00:00 |
|
ValueObjectPrinter.cpp
|
Add a -V <bool> flag to frame variable/expression that enables execution of type validators. The jury is still out on what the user experience of type validators should be, so for now gate it on a specific flag. The mode I am using is prefix variables that fail to validate with a bang, and then emitting the actual validation error on a separate line. Of course, given the total absence of validators, this should never actually happen to you
|
2014-09-06 02:20:19 +00:00 |
e6481c7e0f