summaryrefslogtreecommitdiffstats
path: root/lldb/source/Core/CXXFormatterFunctions.cpp
Commit message (Collapse)AuthorAgeFilesLines
* <rdar://problem/12978143>Enrico Granata2013-01-281-1808/+0
| | | | | | | | | | | Data formatters now cache themselves. This commit provides a new formatter cache mechanism. Upon resolving a formatter (summary or synthetic), LLDB remembers the resolution for later faster retrieval. Also moved the data formatters subsystem from the core to its own group and folder for easier management, and done some code reorganization. The ObjC runtime v1 now returns a class name if asked for the dynamic type of an object. This is required for formatters caching to work with the v1 runtime. Lastly, this commit disposes of the old hack where ValueObjects had to remember whether they were queried for formatters with their static or dynamic type. Now the ValueObjectDynamicValue class works well enough that we can use its dynamic value setting for the same purpose. llvm-svn: 173728
* <rdar://problem/13069948>Greg Clayton2013-01-251-19/+19
| | | | | | | | | | | | Major fixed to allow reading files that are over 4GB. The main problems were that the DataExtractor was using 32 bit offsets as a data cursor, and since we mmap all of our object files we could run into cases where if we had a very large core file that was over 4GB, we were running into the 4GB boundary. So I defined a new "lldb::offset_t" which should be used for all file offsets. After making this change, I enabled warnings for data loss and for enexpected implicit conversions temporarily and found a ton of things that I fixed. Any functions that take an index internally, should use "size_t" for any indexes and also should return "size_t" for any sizes of collections. llvm-svn: 173463
* <rdar://problem/12790664>Enrico Granata2013-01-141-71/+175
| | | | | | Single-character Unicode data formatters llvm-svn: 172492
* <rdar://problem/12239827>Enrico Granata2013-01-121-7/+96
| | | | | | | | | Providing a data formatter for libc++ std::wstring In the process, refactoring the std::string data formatter to be written in C++ so that commonalities between the two can be exploited Also, providing a new API on the ValueObject to navigate a hierarchy by index-path Lastly, an appropriate test case is included llvm-svn: 172282
* Making the Unicode formatters visually nicer by using the same prefix ↵Enrico Granata2013-01-111-11/+11
| | | | | | | | characters as the compiler expects in C++ code Also, marking the Unicode data formatters test cases as dataformatter related for the benefit for the --category flag in dotest.py llvm-svn: 172167
* <rdar://problem/11383764>Enrico Granata2013-01-111-7/+59
| | | | | | Making a data formatter for wchar_t * llvm-svn: 172165
* <rdar://problem/12725746>Enrico Granata2013-01-101-59/+148
| | | | | | | | Providing data formatters for char16_t* and char32_t* C++11-style Unicode strings Using this chance to refactor the UTF data reader used for data formatters for added generality Added a relevant test case llvm-svn: 172119
* <rdar://problem/12848118>Enrico Granata2012-12-101-14/+6
| | | | | | | Making MightHaveChildren() always return true regardless for our own data formatters This is meant to optimize performance for common most-often-not-empty container classes llvm-svn: 169759
* <rdar://problem/12817233>Enrico Granata2012-12-101-1/+1
| | | | | | Change the wording of NSNumber summary from absurd value to unexpected value when a tagged pointer shows up that does not match our knowledge of the internals llvm-svn: 169751
* Fix a few more clang (3.2) warnings on Linux:Daniel Malea2012-12-071-1/+1
| | | | | | | | | | | | | | | | | - remove unused members - add NO_PEDANTIC to selected Makefiles - fix return values (removed NULL as needed) - disable warning about four-char-constants - remove unneeded const from operator*() declaration - add missing lambda function return types - fix printf() with no format string - change sizeof to use a type name instead of variable name - fix Linux ProcessMonitor.cpp to be 32/64 bit friendly - disable warnings emitted by swig-generated C++ code Patch by Matt Kopec! llvm-svn: 169645
* Fix Linux build warnings due to redefinition of macros:Daniel Malea2012-12-051-0/+2
| | | | | | | | | - add new header lldb-python.h to be included before other system headers - short term fix (eventually python dependencies must be cleaned up) Patch by Matt Kopec! llvm-svn: 169341
* In the data formatters, if we know the resultSean Callanan2012-12-041-5/+2
| | | | | | | | | | | | type of an Objective-C selector, don't bother making the expression parser resolve it all over again. Just send the message straight to the object pointer as if it were an id, and cast the result. <rdar://problem/12799087> llvm-svn: 169300
* Resolve printf formatting warnings on Linux:Daniel Malea2012-11-291-10/+10
| | | | | | | | - use macros from inttypes.h for format strings instead of OS-specific types Patch from Matt Kopec! llvm-svn: 168945
* <rdar://problem/11449953> Change Debugger::SetOutputFileHandle() so that it ↵Enrico Granata2012-10-291-0/+64
| | | | | | | | | does not automatically initialize the script interpreter in order to transfer its output file handle to it This should delay initialization of Python until strictly necessary and speed-up debugger startup Also, convert formatters for SEL and BOOL ObjC data-types from Python to C++, in order to reap more performance benefits from the above changes llvm-svn: 166967
* <rdar://problem/12523238> Commit 2 of 3Enrico Granata2012-10-231-4/+12
| | | | | | | | | | | Adding the new has_children (or MightHaveChildren() in C++) for the existing synthetic children providers In a few cases, the new call is going to be much more efficient than the previous num_children > 0 check When the optimization was marginal (e.g. std::vector<>), the choice was to use num_children in order to keep implementation details in one function instead of duplicating code Next step is to provide test cases llvm-svn: 166506
* <rdar://problem/12523238> Commit 1 of 3Enrico Granata2012-10-231-0/+36
| | | | | | | | | | | | This commit enables the new HasChildren() feature for synthetic children providers Namely, it hooks up the required bits and pieces so that individual synthetic children providers can implement a new (optional) has_children call Default implementations have been provided where necessary so that any existing providers continue to work and behave correctly Next steps are: 2) writing smart implementations of has_children for our providers whenever possible 3) make a test case llvm-svn: 166495
* Add the ability to set timeout & "run all threads" options both from the ↵Jim Ingham2012-10-161-5/+5
| | | | | | | | | | "expr" command and from the SB API's that evaluate expressions. <rdar://problem/12457211> llvm-svn: 166062
* <rdar://problem/12462575> Refactoring a block of shared code in the NSString ↵Enrico Granata2012-10-091-146/+59
| | | | | | data formatter llvm-svn: 165557
* <rdar://problem/12424824> Making sure that we correctly update our synthetic ↵Enrico Granata2012-10-041-65/+81
| | | | | | children provider for NSDictionary - providing better support for dynamic types by letting the filter recalculate itself when the type of the object changes llvm-svn: 165260
* <rdar://problem/12424824> Making sure that we correctly update our synthetic ↵Enrico Granata2012-10-041-54/+68
| | | | | | children provider for NSArray - the same work will need to be done for NSDictionary llvm-svn: 165252
* <rdar://problem/12099592> Adding back a bunch of code-running summariesEnrico Granata2012-10-031-0/+7
| | | | llvm-svn: 165186
* <rdar://problem/12349509> Renaming the structure that we use for ↵Enrico Granata2012-10-011-3/+3
| | | | | | NSDictionary children llvm-svn: 164973
* <rdar://problem/12378910> Fix a bunch of other places where similar problems ↵Enrico Granata2012-09-291-0/+23
| | | | | | could happen llvm-svn: 164871
* <rdar://problem/12378910> Fixing a potential crasher in the data formatters ↵Enrico Granata2012-09-291-0/+3
| | | | | | where we fail to check for NULL or empty class name llvm-svn: 164870
* <rdar://problem/11988289> Making C++ synthetic children provider for ↵Enrico Granata2012-09-181-0/+356
| | | | | | NSDictionary and related classes llvm-svn: 164144
* Fixing a typoEnrico Granata2012-09-131-1/+0
| | | | llvm-svn: 163852
* <rdar://problem/11086338> Implementing support for synthetic children ↵Enrico Granata2012-09-131-17/+375
| | | | | | generated by running C++ code instead of Python scripts ; Adding a bunch of value-generating APIs to our private code layer ; Providing synthetic children for NSArray llvm-svn: 163818
* Implementing an Options class for EvaluateExpression() in order to make the ↵Enrico Granata2012-09-051-12/+18
| | | | | | signature more compact and make it easy to 'just run an expression' llvm-svn: 163239
* Adding to files that were missing in the previous commitEnrico Granata2012-09-041-0/+680
llvm-svn: 163156
OpenPOWER on IntegriCloud