Lines Matching full:can

42 Options can be placed anywhere on the command line, but if the arguments begin
77 To set the same file and line breakpoint in LLDB you can enter either of:
84 To set a breakpoint on a function named ``foo`` in LLDB you can enter either of:
91 You can use the ``--name`` option multiple times to make a breakpoint on a set of
99 Setting breakpoints by name is even more specialized in LLDB as you can specify
101 breakpoint on all C++ methods named ``foo`` you can enter either of:
109 To set a breakpoint Objective-C selectors named ``alignLeftEdges:`` you can enter either of:
116 You can limit any breakpoints to a specific executable image by using the
124 The ``--shlib`` option can also be repeated to specify several shared libraries.
139 command can have different completers, so for instance, the ``--file <path>``
141 to currently loaded shared libraries, etc. You can even do things like if you
145 The individual commands are pretty extensively documented. You can use the ``help``
158 You can do:
176 since LLDB reads the file ``~/.lldbinit`` at startup, you can store all your
178 also documented in the ``help`` command so you can remind yourself of what you have
187 one of our aliases, you can easily get rid of it by running, for example:
193 You can also do:
199 So you can run the native LLDB breakpoint command with just ``b``.
208 commands still can have options, if your command string has dashes in it,
215 introduce with the ``define`` command can be done by writing Python functions
222 First you need to set the program to debug. As with GDB, you can start LLDB and
230 Or you can specify it after the fact with the ``file`` command:
241 We have discussed how to set breakpoints above. You can use ``help breakpoint set``
249 You can find out about the breakpoints you have set with:
287 could not find any locations that match the specification. You can tell whether
290 you can tell you have made a typo more easily, if that was indeed the reason no
299 You can delete, disable, set conditions and ignore counts either on all the
312 commands. You can also specify this explicitly by passing the ``--command``
329 you can get further help on from the command system. So in this case you could
366 Then when you have made all your breakpoints, you can set up or modify the options
383 Then you can apply the name to your breakpoints, and they will all pick up
389 You can make breakpoint names in your ``.lldbinit`` file, so you can use them to
390 can behaviors that you have found useful and reapply them in future sessions.
392 You can also make a breakpoint name from the options set on a breakpoint:
403 In addition to breakpoints, you can use help watchpoint to see all the commands
463 You can also attach to a process by process ID or process name. When attaching
492 After launching, you can continue until you hit your breakpoint. The primitive commands
502 At present you can only operate on one thread at a time, but the design will
565 and hit a breakpoint during the evaluation of that code, you can examine
570 You can examine the state of the operations stack using the ``thread plan list``
572 next to continue running, you can remove it with the ``thread plan discard``
606 the ``--no-stdin`` mode, you can set this as a generic process property using the
618 the most part anywhere you can specify a setting on a generic entity (threads,
619 for example) you can also apply the option to a particular instance. You can
631 To inspect the current state of your process, you can start with the threads:
660 You can also provide a list of threads to backtrace, or the keyword ``all`` to see all threads:
666 You can select the current thread, which will be used by default in all the
701 You can also pass in a path to some sub-element of one of the available locals,
711 overloaded operators). The array brackets can be used on pointers to treat
735    You can select another frame to view with the "frame select" command
740 You can also move up and down the stack by passing the ``--relative`` (``-r``) option.