Lines Matching full:python
1 Python Reference
4 The entire LLDB API is available as Python functions through a script bridging
5 interface. This means the LLDB API's can be used directly from python either
6 interactively or to build python apps that provide debugger features.
8 Additionally, Python can be used as a programmatic interface within the lldb
19 The LLDB API is contained in a python module named lldb. A useful resource when
20 writing Python extensions is the lldb Python classes reference guide.
31 lldb - The lldb module contains the public APIs for Python binding.
34 … /System/Library/PrivateFrameworks/LLDB.framework/Versions/A/Resources/Python/lldb/__init__.py
57 Or you can get help using any python object, here we use the lldb.process
77 Embedded Python Interpreter
80 The embedded python interpreter can be accessed in a variety of ways from
87 Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.
94 This drops you into the embedded python interpreter. When running under the
139 Moreover, they are only defined and meaningful while in the interactive Python
141 you should not use them when defining Python formatters, breakpoint scripts and
142 commands (or any other Python extension point that LLDB provides). For the
152 all of the lldb Python objects are able to briefly describe themselves when you
153 pass them to the Python print function:
158 Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.
171 Running a python script when a breakpoint gets hit
174 One very powerful use of the lldb Python API is to have a python script run
175 when a breakpoint gets hit. Adding python scripts to breakpoints provides a way
179 When your process hits a breakpoint to which you have attached some python
212 …nternal_dict`` | ``dict`` | The python session dictionary as a standard pytho…
215 Optionally, a Python breakpoint command can return a value. Returning False
223 An example will show how simple it is to write some python code and attach it
250 (lldb) breakpoint command add --script-type python 1
251 Enter your Python command(s). Type 'DONE' to end.
252 > # Increment our counter. Since we are in a function, this must be a global python variable
265 The breakpoint command add command above attaches a python script to breakpoint 1. To remove the br…
272 Using the python api's to create custom breakpoints
276 Another use of the Python API's in lldb is to create a custom breakpoint
343 The custom Resolver is provided as a Python class with the following methods:
426 Using the python API' to create custom stepping logic
429 A slightly esoteric use of the Python API's is to construct custom stepping
431 simple state machine that runs the plans. You can create a Python class that
438 https://github.com/llvm/llvm-project/blob/main/lldb/examples/python/scripted_step.py
447 To implement a scripted step, you define a python class that has the following
489 Create a new lldb command using a Python function
492 Python functions can be used to create new LLDB command interpreter commands,
496 To write a python function that implements a new LLDB command define the
504 Optionally, you can also provide a Python docstring, and LLDB will use it when providing help for y…
512 Since lldb 3.5.2, LLDB Python commands can also take an SBExecutionContext as an
530 | ``command`` | ``python string`` | A python string containing all arguments for…
539 … | that needs to be printed as a result of the command. The plain Python "print" command al…
542 | ``internal_dict`` | ``python dict object`` | The dictionary for the current embedded scri…
546 Since lldb 3.7, Python commands can also be implemented by means of a class
555 this is the actual bulk of the command, akin to Python command functions
563 As a convenience, you can treat the result object as a Python file object, and
571 providing write() and flush() calls at the Python layer.
590 The standard test for ``__main__``, like many python modules do, is useful for
616 a function that can be used by LLDB's python command code:
620 #!/usr/bin/env python
633 print 'The "ls" python command has been installed and is ready for use.'
641 The "ls" python command has been installed and is ready for use.
656 #!/usr/bin/env python
671 …print('The "my-utilities" python command has been installed and its subcommands are ready for use.…
695 https://github.com/llvm/llvm-project/blob/main/lldb/examples/python/cmdtemplate.py
725 Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.
737 Using the lldb.py module in Python
744 bindings from LLDB into Python. To use the LLDB.framework to create your own
745 stand-alone python programs, you will need to tell python where to look in
747 variable, adding a path to the directory that contains the lldb.py python
763 Alternately, you can append the LLDB Python directory to the sys.path list
764 directly in your Python code before importing the lldb module.
766 Now your python scripts are ready to import the lldb module. Below is a python
773 #!/usr/bin/env python
839 Writing lldb frame recognizers in Python
847 Adding a custom frame recognizer is done by implementing a Python class and
848 using the 'frame recognizer add' command. The Python class should have a
891 Writing Target Stop-Hooks in Python:
896 be implemented by a suitably defined Python class. The Python based stop-hooks
899 constructor of the Python object managing the stop hook. This allows for
902 To add a Python-based stop hook, first define a class with the following methods: