Lines Matching +full:- +full:- +full:-
10 Of course, in this context it has full access to the LLDB API - with some
17 --------------
31 lldb - The lldb module contains the public APIs for Python binding.
78 ---------------------------
87 Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.
101 …-------------------+---------------------+-------------------------------------+------------------…
103 …-------------------+---------------------+-------------------------------------+------------------…
108 …-------------------+---------------------+-------------------------------------+------------------…
109 …SBDebugger.GetSelectedTarget` | Contains the currently selected target - for instance the one…
110 … | ``file`` or selected by the ``target select <target-index>`` command. …
113 …-------------------+---------------------+-------------------------------------+------------------…
117 …-------------------+---------------------+-------------------------------------+------------------…
121 … | | The ``thread select <thread-index>`` command can …
124 …-------------------+---------------------+-------------------------------------+------------------…
129 … | | The ``frame select <frame-index>`` command can …
132 …-------------------+---------------------+-------------------------------------+------------------…
158 Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.
172 --------------------------------------------------
196 …-------------------+-------------------------------+----------------------------------------------…
198 …-------------------+-------------------------------+----------------------------------------------…
202 …-------------------+-------------------------------+----------------------------------------------…
206 …-------------------+-------------------------------+----------------------------------------------…
209 …field in the ``extra_args``, making the callback more general. The ``-k`` and ``-v`` options |
211 …-------------------+-------------------------------+----------------------------------------------…
213 …-------------------+-------------------------------+----------------------------------------------…
241 one-line version of the script command.
247 (lldb) breakpoint set --func-regex=. --shlib=libfoo.dylib
250 (lldb) breakpoint command add --script-type python 1
273 ---------------------------------------------------
281 breakpoint locations - the actual places where the breakpoint will trigger. To
301 the -s modulename flag to break set you are creating a Module-based search
302 filter. When you pass -f filename.c to break set -n you are creating a file
304 a no-op search filter, so all parts of the program are searched and all
345 …--------------------+---------------------------------------+-------------------------------------…
347 …--------------------+---------------------------------------+-------------------------------------…
358 …--------------------+---------------------------------------+-------------------------------------…
369 …--------------------+---------------------------------------+-------------------------------------…
380 …--------------------+---------------------------------------+-------------------------------------…
383 …--------------------+---------------------------------------+-------------------------------------…
390 (lldb) breakpoint set -P MyModule.MyResolverClass
397 (lldb) breakpoint set -P MyModule.MyResolverClass -k key_1 -v value_1 -k key_2 -v value_2
403 passing the -s ModuleName option - which can be specified multiple times. You
405 in the -f CompUnitName option. This can also be specified more than once. And
411 (lldb) breakpoint set -P MyModule.MyResolverClass -s a.out
427 -----------------------------------------------------
438 https://github.com/llvm/llvm-project/blob/main/lldb/examples/python/scripted_step.py
442 https://github.com/llvm/llvm-project/blob/main/lldb/include/lldb/Target/ThreadPlan.h
450 +-------------------+------------------------------------+-----------------------------------------…
452 +-------------------+------------------------------------+-----------------------------------------…
456 +-------------------+------------------------------------+-----------------------------------------…
458 +-------------------+------------------------------------+-----------------------------------------…
463 +-------------------+------------------------------------+-----------------------------------------…
466 +-------------------+------------------------------------+-----------------------------------------…
471 +-------------------+------------------------------------+-----------------------------------------…
477 (lldb) thread step-scripted -C MyModule.MyStepPlanClass
481 in/out/over and run-to-address) in front of itself on the stack, which can be
486 while performing the step-over.
490 -------------------------------------------------
514 independent of the currently-selected entities in the debugger.
516 This feature is enabled if the command-implementing function can be recognized
525 …-------------------+--------------------------------+---------------------------------------------…
527 …-------------------+--------------------------------+---------------------------------------------…
529 …-------------------+--------------------------------+---------------------------------------------…
533 …-------------------+--------------------------------+---------------------------------------------…
537 …-------------------+--------------------------------+---------------------------------------------…
541 …-------------------+--------------------------------+---------------------------------------------…
544 …-------------------+--------------------------------+---------------------------------------------…
553 …ll should initialize the command with respect to the command interpreter for the passed-in debugger
570 SBCommandReturnObject and SBStream both support this file-like behavior by
573 One other handy convenience when defining lldb command-line commands is the
632 debugger.HandleCommand('command script add -f ls.ls ls')
642 (lldb) ls -l /tmp/
644 -rw-r--r--@ 1 someuser wheel 6148 Jan 19 17:27 .DS_Store
645 -rw------- 1 someuser wheel 7331 Jan 19 15:37 crash.log
648 lldb. Most of the lldb built-in commands structure themselves this way, and using
649 a tree structure has the benefit of leaving the one-word command space free for user
652 "my-utilities" container:
668 debugger.HandleCommand('command container add -h "A container for my utilities" my-utilities')
669 …debugger.HandleCommand('command script add -f my_utilities.first_utility -h "My first utility" my-…
670 …debugger.HandleCommand('command script add -f my_utilities.second_utility -h "My second utility" m…
671 …print('The "my-utilities" python command has been installed and its subcommands are ready for use.…
673 Then your new commands are available under the my-utilities node:
677 (lldb) help my-utilities
680 Syntax: my-utilities
684 first -- My first utility Expects 'raw' input (see 'help raw-input'.)
685 second -- My second utility Expects 'raw' input (see 'help raw-input'.)
688 (lldb) my-utilities first
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.
731 (lldb) command script add pofoo -f pofoo_funct
738 ----------------------------------
745 stand-alone python programs, you will need to tell python where to look in
755 % setenv PYTHONPATH `lldb -P`
761 $ export PYTHONPATH=`lldb -P`
840 ----------------------------------------
877 (lldb) frame recognizer add -l fd_recognizer.LibcFdRecognizer -n read -s libsystem_kernel.dylib
886 * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.3
891 Writing Target Stop-Hooks in Python:
892 ------------------------------------
895 user. Stop hooks can either be a set of lldb command-line commands, or can
896 be implemented by a suitably defined Python class. The Python based stop-hooks
897 can also be passed as set of -key -value pairs when they are added, and those
902 To add a Python-based stop hook, first define a class with the following methods:
904 …--------------------+---------------------------------------+-------------------------------------…
906 …--------------------+---------------------------------------+-------------------------------------…
907 …rget: lldb.SBTarget`` | This is the constructor for the new stop-hook. …
913 … | breakpoint. It is not required, but allows for reuse of stop-hook classes. …
914 …--------------------+---------------------------------------+-------------------------------------…
923 …es to stop. If it returns False, then the thread votes to continue after all the stop-hooks |
925 … | | Note, the --auto-continue flag to 'target stop-hoo…
926 …--------------------+---------------------------------------+-------------------------------------…
933 (lldb) target stop-hook add -P MyModule.MyStopHook -k first -v 1 -k second -v 2