summaryrefslogtreecommitdiffstats
path: root/lldb/examples/python/lldbtk.py
Commit message (Collapse)AuthorAgeFilesLines
* Python 2/3 compat: tkinterSerge Guelton2019-03-251-2/+7
| | | | | | Differential Revision: https://reviews.llvm.org/D59586 llvm-svn: 356909
* Python 2/3 compatibility: from __future__ import print_functionSerge Guelton2019-03-211-7/+7
| | | | | | Differential Revision: https://reviews.llvm.org/D59580 llvm-svn: 356695
* *** This commit represents a complete reformatting of the LLDB source codeKate Stone2016-09-061-148/+217
| | | | | | | | | | | | | | | | | | | | | | | *** 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
* Improved the TreeItem delegate which simplifies making tree items:Greg Clayton2014-10-071-135/+419
| | | | | | | | - tree items can define any number of key/value pairs - creating a tree you specify which columns you want to display and it will pick out the right key/value pairs from the new tree item dictionaries - added new "tk-target" command to explore the target's images, sections, symbols, compile units and line tables. llvm-svn: 219219
* Played around with TK UI a bit this weekend.Greg Clayton2014-09-221-0/+260
If you "command script import" this file, then you will have two new commands: (lldb) tk-variables (lldb) tk-process Not sure how this will work on all other systems, but on MacOSX, you will get a window with a tree view that allows you to inspect your local variables by expanding variables to see the child values. The "tk-process" allows you to inspect the currently selected process by expanding the process to see the threads, the threads to see the frames, and the frames to see the variables. Very handy if you want to view variables for all frames simultaneously. llvm-svn: 218279
OpenPOWER on IntegriCloud