llvm-project.git/lldb/examples/python/shadow.py, branch main Unnamed repository; edit this file 'description' to name the repository. [NFC][Py Reformat] Reformat python files in lldb 2023-05-25T19:54:09+00:00 Jonas Devlieghere jonas@devlieghere.com 2023-05-25T15:48:57+00:00 2238dcc39358353cac21df75c3c3286ab20b8f53 This is an ongoing series of commits that are reformatting our Python code. Reformatting is done with `black` (23.1.0). If you end up having problems merging this commit because you have made changes to a python file, the best way to handle that is to run `git checkout --ours <yourfile>` and then reformat it with black. RFC: https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style Differential revision: https://reviews.llvm.org/D151460 
This is an ongoing series of commits that are reformatting our Python
code. Reformatting is done with `black` (23.1.0).

If you end up having problems merging this commit because you have made
changes to a python file, the best way to handle that is to run `git
checkout --ours <yourfile>` and then reformat it with black.

RFC: https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style

Differential revision: https://reviews.llvm.org/D151460
[LLDB] Remove __future__ imports from examples 2022-08-15T09:04:25+00:00 David Spickett david.spickett@linaro.org 2022-08-12T13:14:00+00:00 9f947abf94e16fa7c759ab56a4fb030d6ef25961 Not needed now that we require python 3. Reviewed By: kastiglione, JDevlieghere Differential Revision: https://reviews.llvm.org/D131772 
Not needed now that we require python 3.

Reviewed By: kastiglione, JDevlieghere

Differential Revision: https://reviews.llvm.org/D131772
Harmonize Python shebang 2020-07-16T19:53:45+00:00 serge-sans-paille sguelton@redhat.com 2020-07-15T07:31:13+00:00 515bc8c1554f03515565878ea3d35cffdc6fd195 Differential Revision: https://reviews.llvm.org/D83857 
Differential Revision: https://reviews.llvm.org/D83857
Python 2/3 compatibility: from __future__ import print_function 2019-03-21T18:27:40+00:00 Serge Guelton sguelton@redhat.com 2019-03-21T18:27:40+00:00 525cd59f5a12254e80d5f20bf2d9713728a114d4 Differential Revision: https://reviews.llvm.org/D59580 llvm-svn: 356695 
Differential Revision: https://reviews.llvm.org/D59580

llvm-svn: 356695
*** This commit represents a complete reformatting of the LLDB source code 2016-09-06T20:57:50+00:00 Kate Stone katherine.stone@apple.com 2016-09-06T20:57:50+00:00 b9c1b51e45b845debb76d8658edabca70ca56079 *** 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 
*** 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
Fixup the "shadow" example command to use the function that takes an execution context now that the @lldb.command decorator does the right thing for the command function that takes 5 arguments. 2016-06-28T00:06:35+00:00 Greg Clayton gclayton@apple.com 2016-06-28T00:06:35+00:00 296f166aa3d4d051090c0b6061e964e4a15e4ea3 A few fixes: - Check the process state to make sure it is stopped - Grab the frame from the "exe_ctx" so this will work during breakpoint callbacks - Print out the SBDeclaration objects of the variables that shadow each other so we can see the source locations of which variable declarations are shodowing each other. llvm-svn: 273963 
A few fixes:
- Check the process state to make sure it is stopped
- Grab the frame from the "exe_ctx" so this will work during breakpoint callbacks
- Print out the SBDeclaration objects of the variables that shadow each other so we can see the source locations of which variable declarations are shodowing each other.

llvm-svn: 273963
Added a new python example which installs a command called "shadow". 2016-06-23T19:54:32+00:00 Greg Clayton gclayton@apple.com 2016-06-23T19:54:32+00:00 fe9d1ee9e45c91fab05c69e672117efd4ed8c0cc This shows how to grab individual blocks from stack frames and get only the variables from those blocks. It then will iterate over all of the parent blocks and look for shadowed variables. llvm-svn: 273604 
This shows how to grab individual blocks from stack frames and get only the variables from those blocks. It then will iterate over all of the parent blocks and look for shadowed variables.

llvm-svn: 273604