summaryrefslogtreecommitdiffstats
path: root/lldb/examples/python/sbvalue.py
Commit message (Collapse)AuthorAgeFilesLines
* *** This commit represents a complete reformatting of the LLDB source codeKate Stone2016-09-061-76/+89
| | | | | | | | | | | | | | | | | | | | | | | *** 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
* Added a new lldb.SBValue helper module that has two classes:Greg Clayton2012-01-301-0/+255
sbvalue.value (<SBValue>) sbvalue.variable (<SBValue>) Initialize both with a lldb.SBValue sbvalue.value() make all sorts of convenience properties. Type "help(sbvalue.value)" in the embedded python interpreter to see what is available. sbvalue.variable() wraps a lldb.SBValue and allows you to play with your variable just as you would expect: pt = sbvalue.variable (lldb.frame.FindVariable("pt")) print pt.x print py.y argv = sbvalue.variable (lldb.frame.FindVariable("argv")) print argv[0] Member access and array acccess is all taken care of! llvm-svn: 149260
OpenPOWER on IntegriCloud