| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Differential Revision: https://reviews.llvm.org/D59589
llvm-svn: 356908
|
|
|
|
| |
llvm-svn: 356904
|
|
|
|
|
|
| |
Differential Revision: https://reviews.llvm.org/D59580
llvm-svn: 356695
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to reflect the new license.
We understand that people may be surprised that we're moving the header
entirely to discuss the new license. We checked this carefully with the
Foundation's lawyer and we believe this is the correct approach.
Essentially, all code in the project is now made available by the LLVM
project under our new license, so you will see that the license headers
include that license only. Some of our contributors have contributed
code under our old license, and accordingly, we have retained a copy of
our old license notice in the top-level files in each project and
repository.
llvm-svn: 351636
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** to conform to clang-format’s LLVM style. This kind of mass change has
*** two obvious implications:
Firstly, merging this particular commit into a downstream fork may be a huge
effort. Alternatively, it may be worth merging all changes up to this commit,
performing the same reformatting operation locally, and then discarding the
merge for this particular commit. The commands used to accomplish this
reformatting were as follows (with current working directory as the root of
the repository):
find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} +
find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ;
The version of clang-format used was 3.9.0, and autopep8 was 1.2.4.
Secondly, “blame” style tools will generally point to this commit instead of
a meaningful prior commit. There are alternatives available that will attempt
to look through this change and find the appropriate prior commit. YMMV.
llvm-svn: 280751
|
|
|
|
|
|
|
|
|
|
| |
Even though these are under examples/, they actually get loaded
when LLDB starts up during initialization of ScriptInterpreterPython.
There's obviously some kind of layering issue here (and comments
in the code even point to that as well), but for now just make them
py3 compatible.
llvm-svn: 250710
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: Another round of minor typo fixes.
Reviewers: clayborg
Subscribers: lldb-commits
Differential Revision: http://reviews.llvm.org/D13026
llvm-svn: 248243
|
|
|
|
|
|
|
|
| |
* transfered => transferred
* unkown => unknown
* sucessfully => successfully
llvm-svn: 215367
|
|
|
|
|
|
| |
Python and reimplements them in C++. The Python Cocoa formatters are not shipped as part of LLDB anymore, but still exist in the source repository for user reference. Python formatters still exist for STL classes and users can still define their own Python formatters
llvm-svn: 177366
|
|
|
|
| |
llvm-svn: 177217
|
|
|
|
|
|
| |
and NSNotification
llvm-svn: 177213
|
|
|
|
|
|
|
|
| |
If you try to access any child > 0 without having touched child 0, LLDB won't be able to reconstruct type information from the debug info.
Previously, we would fail.
Now, we simply go fetch child 0 and then come back.
llvm-svn: 174795
|
|
|
|
|
|
| |
The vtable pointer field is not necessarily a pointer and hence cannot be used for validation
llvm-svn: 173947
|
|
|
|
| |
llvm-svn: 172641
|
|
|
|
|
|
|
|
| |
unique even in situations where underlying platforms would actually duplicate or hardcode PIDs
The Python data formatters use a per-process cache that was previously keying off the PID. Moving that to be based on this new notion of unique ID.
llvm-svn: 172633
|
|
|
|
|
|
| |
doing the right thing, but the comment was highly misleading
llvm-svn: 170441
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
relying on SBValue.GetValueAsUnsigned() to reinterpret a double as a uint64_t
llvm-svn: 166610
|
|
|
|
| |
llvm-svn: 165341
|
|
|
|
|
|
| |
zombie objects when attempting to format them
llvm-svn: 164156
|
|
|
|
|
|
| |
UUIDs
llvm-svn: 164151
|
|
|
|
|
|
| |
indexes instead of objects
llvm-svn: 164149
|
|
|
|
| |
llvm-svn: 163162
|
|
|
|
|
|
| |
CFString summary errors
llvm-svn: 163157
|
|
|
|
|
|
| |
the Objective-C language runtime plugin expose class descriptors objects akin to the objc_runtime.py Pythonic implementation. Rewrite the data formatters for some core Cocoa classes in C++ instead of Python.
llvm-svn: 163155
|
|
|
|
| |
llvm-svn: 161111
|
|
|
|
|
|
| |
values
llvm-svn: 160179
|
|
|
|
|
|
| |
using True/False as compared to 1/0 for logical values. Wexploit this to our advantage. Other minor tweaks
llvm-svn: 157209
|
|
|
|
| |
llvm-svn: 157066
|
|
|
|
|
|
| |
empty in spite of the string actually having a content
llvm-svn: 156793
|
|
|
|
|
|
| |
Previously, the categories were filled in but disabled by default. Tweaking test cases appropriately to keep working and do the right thing
llvm-svn: 155605
|
|
|
|
| |
llvm-svn: 155586
|
|
|
|
|
|
| |
an issue that was preventing Python oneliners from executing
llvm-svn: 155563
|
|
|
|
|
|
| |
resources - This is one of the steps towards making the data formatters work again
llvm-svn: 155526
|
|
|
|
|
|
|
|
| |
global namespace.
Enrico will follow this up with fixing the data formatter test cases that are failing.
llvm-svn: 155514
|
|
|
|
| |
llvm-svn: 153911
|
|
|
|
| |
llvm-svn: 153910
|
|
|
|
| |
llvm-svn: 153899
|
|
|
|
| |
llvm-svn: 153878
|
|
|
|
|
|
| |
formatters eating up all the stack when an unknown class has to be summarized ; this should make the whole Objective-C summaries more stable
llvm-svn: 153712
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of bug fixing for data formatter issues.
We are introducing a new Logger class on the Python side. This has the same purpose, but is unrelated, to the C++ logging facility
The Pythonic logging can be enabled by using the following scripting commands:
(lldb) script Logger._lldb_formatters_debug_level = {0,1,2,...}
0 = no logging
1 = do log
2 = flush after logging each line - slower but safer
3 or more = each time a Logger is constructed, log the function that has created it
more log levels may be added, each one being more log-active than the previous
by default, the log output will come out on your screen, to direct it to a file:
(lldb) script Logger._lldb_formatters_debug_filename = 'filename'
that will make the output go to the file - set to None to disable the file output and get screen logging back
Logging has been enabled for the C++ STL formatters and for Cocoa class NSData - more logging will follow
synthetic children providers for classes list and map (both libstdcpp and libcxx) now have internal capping for safety reasons
this will fix crashers where a malformed list or map would not ever meet our termination conditions
to set the cap to a different value:
(lldb) script {gnu_libstdcpp|libcxx}.{map|list}_capping_size = new_cap (by default, it is 255)
you can optionally disable the loop detection algorithm for lists
(lldb) script {gnu_libstdcpp|libcxx}.list_uses_loop_detector = False
llvm-svn: 153676
|
|
|
|
|
|
| |
escape sequences by the summary provider shipping with LLDB - Added relevant test case code. Bonus points for identifying the source of the quotes :-)
llvm-svn: 153624
|
|
|
|
| |
llvm-svn: 153559
|
|
|
|
| |
llvm-svn: 153541
|
|
|
|
|
|
| |
things-went-wrong situations. Previously they would say nothing or log failures to the Python console
llvm-svn: 152673
|
|
|
|
|
|
|
|
|
|
|
| |
uses internally to provide summaries
This has been done for those summaries where the difference is only cosmetic (e.g. naming things as items instead of values, ...)
The LLDB output style has been preserved when it provides more information (e.g. telling the type as well as the value of an NSNumber)
Test cases have been updated to reflect the updated output style where necessary
llvm-svn: 152592
|
|
|
|
|
|
| |
optimization to the whole Cocoa formatters infrastructure
llvm-svn: 152423
|
|
|
|
| |
llvm-svn: 152358
|
|
|
|
|
|
| |
objects'
llvm-svn: 152186
|
|
|
|
|
|
|
|
|
|
|
|
| |
(a) the SystemParameters object is now passed around to the formatters; doing so enables the formatters to reuse computed values for things such as pointer-size and endianness
instead of repeatedly computing these on their own
(b) replacing the global ISA cache with a per-process one
(c) providing a per-process types cache where each formatter can store the types it needs to operate, and be sure to find them the next time without recalculating them
this also enables formatters to share types if they agree on a local naming convention
(d) lazy fetching of data from Objective-C runtime data structures
data is fetched as needed and we stop reading as soon as we determine that an ISA is actually garbage
llvm-svn: 152052
|