Lines Matching full:command
2 gdb command set:
5 1) LLDB Command Structure:
7 First some details on lldb command structure to help orient you...
9 Unlike gdb's command set, which is rather free-form, we tried to make
10 the lldb command syntax fairly structured. The commands are all of the
15 The command line parsing is done before command execution, so it is
16 uniform across all the commands. The command syntax is very simple,
20 command syntax more regular, but it also means you may have to
23 Options can be placed anywhere on the command line, but if the arguments
25 using the "--" option. So for instance, the "process launch" command takes
35 this is the breakpoint command. In gdb, to set a breakpoint, you
78 Just like gdb, the lldb command interpreter does a shortest unique
79 string match on command names, so the previous command can also be
84 lldb also supports command completion for source file names, symbol
86 Individual options in a command can have different completers, so for
93 the "help" command. And there is an "apropos" command that will
95 for each matching command.
104 (lldb) command alias bfl breakpoint set -f %1 -l %2
114 However, users are free to customize lldb's command set however they
117 you. Your aliases are also documented in the help command so you can
121 the "script" command. All the functionality of the debugger is
123 commands that in gdb you would introduce with the "define" command can
126 with the "script" command.
137 on the command line:
142 or you can specify it after the fact with the "file" command:
198 your specification resolved to. For instance if we wanted to add a command
201 (lldb) b command add -c 1.1
202 Enter your debugger command(s). Type 'DONE' to end.
206 The "-c" option specifies that the breakpoint command is a set of lldb
207 command interpreter commands. Use "-s" if you want to implement your
208 breakpoint command using the Python interface instead.
213 Then you can either launch the process with the command:
247 commands for process control all exist under the "thread" command:
285 close equivalent to gdb's "until" command.
369 The frame variable command is not a full expression parser but it
383 The frame variable command will also perform "object printing" operations on
408 use the general "expression" command. It takes an expression and
425 take "raw" input. "expression" is one of these. So in the expression command,
441 (lldb) command alias pwd script print os.getcwd()
442 (lldb) command regex cd "s/^(.*)$/script os.chdir(os.path.expanduser('%1'))/"
452 Or for a more capable 'cd' command, create ~/utils.py like this:
470 command alias pwd script print os.getcwd()
471 command script add -f utils.chdir cd
