summaryrefslogtreecommitdiffstats
path: root/lldb/examples/python/shadow.py
diff options
context:
space:
mode:
authorKate Stone <katherine.stone@apple.com>2016-09-06 20:57:50 +0000
committerKate Stone <katherine.stone@apple.com>2016-09-06 20:57:50 +0000
commitb9c1b51e45b845debb76d8658edabca70ca56079 (patch)
treedfcb5a13ef2b014202340f47036da383eaee74aa /lldb/examples/python/shadow.py
parentd5aa73376966339caad04013510626ec2e42c760 (diff)
downloadbcm5719-llvm-b9c1b51e45b845debb76d8658edabca70ca56079.tar.gz
bcm5719-llvm-b9c1b51e45b845debb76d8658edabca70ca56079.zip
*** This commit represents a complete reformatting of the LLDB source code
*** 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
Diffstat (limited to 'lldb/examples/python/shadow.py')
-rw-r--r--lldb/examples/python/shadow.py13
1 files changed, 7 insertions, 6 deletions
diff --git a/lldb/examples/python/shadow.py b/lldb/examples/python/shadow.py
index d1a5878fcef..0556cfc553c 100644
--- a/lldb/examples/python/shadow.py
+++ b/lldb/examples/python/shadow.py
@@ -3,14 +3,16 @@
import lldb
import shlex
+
@lldb.command("shadow")
def check_shadow_command(debugger, command, exe_ctx, result, dict):
'''Check the currently selected stack frame for shadowed variables'''
process = exe_ctx.GetProcess()
state = process.GetState()
if state != lldb.eStateStopped:
- print >>result, "process must be stopped, state is %s" % lldb.SBDebugger.StateAsCString(state)
- return
+ print >>result, "process must be stopped, state is %s" % lldb.SBDebugger.StateAsCString(
+ state)
+ return
frame = exe_ctx.GetFrame()
if not frame:
print >>result, "invalid frame"
@@ -18,10 +20,10 @@ def check_shadow_command(debugger, command, exe_ctx, result, dict):
# Parse command line args
command_args = shlex.split(command)
# TODO: add support for using arguments that are passed to this command...
-
+
# Make a dictionary of variable name to "SBBlock and SBValue"
shadow_dict = {}
-
+
num_shadowed_variables = 0
# Get the deepest most block from the current frame
block = frame.GetBlock()
@@ -40,7 +42,7 @@ def check_shadow_command(debugger, command, exe_ctx, result, dict):
shadow_dict[block_var_name].append(block_var)
else:
shadow_dict[block_var_name] = [block_var]
- # Get the parent block and continue
+ # Get the parent block and continue
block = block.GetParent()
num_shadowed_variables = 0
@@ -54,4 +56,3 @@ def check_shadow_command(debugger, command, exe_ctx, result, dict):
print >>result, str(shadow_var.GetDeclaration())
if num_shadowed_variables == 0:
print >>result, 'no variables are shadowed'
-
OpenPOWER on IntegriCloud