Lines Matching refs:commands

14 …e-form, we tried to make the lldb command syntax fairly structured. The commands are all of the fo…
21 across all the commands. The command syntax for basic commands is very simple,
59 commands are more verbose but also more precise and allow for intelligent auto
78 conditions or commands without having to specify them multiple times:
114 on command names, so the following two commands will both execute the same
130 The individual commands are pretty extensively documented. You can use the help
131 command to get an overview of which commands are available or to obtain details
132 about specific commands. There is also an apropos command that will search the
133 help text for all commands for a particular word and dump a summary help string
136 Finally, there is a mechanism to construct aliases for commonly used commands.
150 We have added a few aliases for commonly used commands (e.g. "step", "next" and
152 is more convenient to make the basic commands unique down to a letter or two,
167 the way of the rest of the breakpoint commands. Fortunately, if you don't like
182 The lldb command parser also supports "raw" commands, where, after command
184 uninterpreted to the command. This is convenient for commands whose arguments
189 commands still can have options, if your command string has dashes in it,
195 in the Python interpreter, so the more complex commands that in gdb you would
298 commands. You can also specify this explicitly by passing the "--command"
308    Add a set of commands to a breakpoint, to be executed whenever the breakpoint is hit.
313 When you see arguments to commands specified in the Syntax in angle brackets
327 …o react when the breakpoint is hit. The latter set of information (e.g. commands, conditions, hit-…
379 In addition to breakpoints, you can use help watchpoint to see all the commands
467 After launching, we can continue until we hit our breakpoint. The primitive commands for process co…
476 …l be particularly important. For convenience, however, all the stepping commands have easy aliases…
478 The other program stepping commands are pretty much the same as in gdb. You've got:
486 By default, lldb does defined aliases to all common gdb process control commands ("s", "step", "n",…
512 the command interpreter is always available to enter commands. It might be a
522 There are many commands that won't work while running, and the command
530 The commands that currently work while running include interrupting the process
561 always the bottom-most frame). Many the commands for inspecting state work on
600 commands in the next section, with the "thread select" command: