Lines Matching refs:can

29 Options can be placed anywhere on the command line, but if the arguments begin
62 To set the same file and line breakpoint in LLDB you can enter either of:
69 To set a breakpoint on a function named foo in LLDB you can enter either of:
76 You can use the --name option multiple times to make a breakpoint on a set of
84 Setting breakpoints by name is even more specialized in LLDB as you can specify
86 breakpoint on all C++ methods named foo you can enter either of:
94 To set a breakpoint Objective-C selectors named alignLeftEdges: you can enter either of:
101 You can limit any breakpoints to a specific executable image by using the
109 The --shlib option can also be repeated to specify several shared libraries.
124 command can have different completers, so for instance, the "--file <path>"
126 to currently loaded shared libraries, etc. We can even do things like if you
130 The individual commands are pretty extensively documented. You can use the help
143 you can do:
157 since lldb reads the file ~/.lldbinit at startup, you can store all your
159 also documented in the help command so you can remind yourself of what you've
168 one of our aliases, you can easily get rid of it by running (for example):
180 so I can run the native lldb breakpoint command with just b
189 commands still can have options, if your command string has dashes in it,
196 introduce with the "define" command can be done by writing Python functions
207 First we need to set the program to debug. As with gdb, you can start lldb and specify the file you…
214 or you can specify it after the fact with the "file" command:
225 We've discussed how to set breakpoints above. You can use help breakpoint set
233 You can find out about the breakpoints you've set with:
272 couldn't find any locations that match the specification. You can tell whether
275 you can tell you've made a typo more easily, if that was indeed the reason no
285 You can delete, disable, set conditions and ignore counts either on all the
298 commands. You can also specify this explicitly by passing the "--command"
315 you can get further help on from the command system. So in this case you could
343 Then when you've made all your breakpoints, you can set up or modify the options using the name to …
359 Then you can apply the name to your breakpoints, and they will all pick up
365 You can make breakpoint names in your .lldbinit file, so you can use them to
366 can behaviors that you have found useful and reapply them in future sessions.
368 You can also make a breakpoint name from the options set on a breakpoint:
379 In addition to breakpoints, you can use help watchpoint to see all the commands
438 You can also attach to a process by process ID or process name. When attaching
467 After launching, we can continue until we hit our breakpoint. The primitive commands for process co…
476 At present you can only operate on one thread at a time, but the design will ultimately support say…
538 the --no-stdin mode, you can set this as a generic process property using the
550 the most part anywhere you can specify a setting on a generic entity (threads,
551 for example) you can also apply the option to a particular instance, which can
552 also be convenient at times. You can view the available settings with "settings
564 To inspect the current state of your process, you can start with the threads:
593 You can also provide a list of threads to backtrace, or the keyword "all" to see all threads:
599 You can select the current thread, which will be used by default in all the
634 You can also pass in a path to some subelement of one of the available locals,
644 overloaded operators). The array brackets can be used on pointers to treat
668    You can select another frame to view with the "frame select" command
673 You can also move up and down the stack by passing the "--relative" ("-r") option. And we have buil…