Lines Matching refs:breakpoint
42 intentions. The first instance you'll note of this is the breakpoint command.
43 In gdb, to set a breakpoint, you might enter
62 To set the same file and line breakpoint in LLDB you can enter either of:
66 (lldb) breakpoint set --file foo.c --line 12
67 (lldb) breakpoint set -f foo.c -l 12
69 To set a breakpoint on a function named foo in LLDB you can enter either of:
73 (lldb) breakpoint set --name foo
74 (lldb) breakpoint set -n foo
76 You can use the --name option multiple times to make a breakpoint on a set of
82 (lldb) breakpoint set --name foo --name bar
85 that you want to set a breakpoint at a function by method name. To set a
86 breakpoint on all C++ methods named foo you can enter either of:
90 (lldb) breakpoint set --method foo
91 (lldb) breakpoint set -M foo
94 To set a breakpoint Objective-C selectors named alignLeftEdges: you can enter either of:
98 (lldb) breakpoint set --selector alignLeftEdges:
99 (lldb) breakpoint set -S alignLeftEdges:
106 (lldb) breakpoint set --shlib foo.dylib --name foo
107 (lldb) breakpoint set -s foo.dylib -n foo
119 (lldb) breakpoint set -n "-[SKTGraphicView alignLeftEdges:]"
125 option in "breakpoint" completes to source files, the "--shlib <path>" option
141 (lldb) breakpoint set --file foo.c --line 12
147 (lldb) command alias bfl breakpoint set -f %1 -l %2
167 the way of the rest of the breakpoint commands. Fortunately, if you don't like
178 (lldb) command alias b breakpoint
180 so I can run the native lldb breakpoint command with just b
225 We've discussed how to set breakpoints above. You can use help breakpoint set
226 to see all the options for breakpoint setting. For instance, we might do:
230 (lldb) breakpoint set --selector alignLeftEdges:
237 (lldb) breakpoint list
243 Note that setting a breakpoint creates a logical breakpoint, which could
245 breakpoint on all the methods that implement that selector in the classes in
246 your program. Similarly, a file and line breakpoint might result in multiple
249 The logical breakpoint has an integer id, and its locations have an id within
250 their parent breakpoint (the two are joined by a ".", e.g. 1.1 in the example
255 the new location would be added to breakpoint 1 (e.g. a "1.2" breakpoint would
258 The other piece of information in the breakpoint listing is whether the
259 breakpoint location was resolved or not. A location gets resolved when the file
261 instance if you set a breakpoint in a shared library that then gets unloaded,
262 that breakpoint location will remain, but it will no longer be resolved.
269 (gdb) set breakpoint pending on
271 That is, lldb will always make a breakpoint from your specification, even if it
274 "breakpoint list", and we report the breakpoint as "pending" when you set it so
281 (lldb) breakpoint set --file foo.c --line 12
283 WARNING: Unable to resolve breakpoint to any actual locations.
286 locations generated by your logical breakpoint, or on any one of the particular
288 command to print a backtrace when we hit this breakpoint we could do:
292 (lldb) breakpoint command add 1.1
297 By default, the breakpoint command add command takes lldb command line
299 option. Use "--script" if you want to implement your breakpoint command using
308 Add a set of commands to a breakpoint, to be executed whenever the breakpoint is hit.
310 Syntax: breakpoint command add <cmd-options> <breakpt-id>
327 …breakpoint, and the other how to react when the breakpoint is hit. The latter set of information (…
333 (lldb) breakpoint modify -c "self == nil" -C bt --auto-continue 1 2 3
335 That's not too bad, but you have to repeat this for every new breakpoint you make, and if you wante…
337 …breakpoints you want to affect this way into a group. So when you make the breakpoint you would do:
341 (lldb) breakpoint set -N SelfNil
347 (lldb) breakpoint modify -c "self == nil" -C bt --auto-continue SelfNil
353 A even better solution is to make a fully configured breakpoint name:
357 (lldb) breakpoint name configure -c "self == nil" -C bt --auto-continue SelfNil
365 You can make breakpoint names in your .lldbinit file, so you can use them to
368 You can also make a breakpoint name from the options set on a breakpoint:
372 (lldb) breakpoint name configure -B 1 SelfNil
374 which makes it easy to copy behavior from one breakpoint to a set of others.
460 one thread to hit your breakpoint(s) before the kernel actually returns control
467 After launching, we can continue until we hit our breakpoint. The primitive commands for process co…
514 you to set a breakpoint, etc without having to explicitly interrupt the
520 (lldb) breakpoint set --name stop_here
532 status"), breakpoint setting and clearing (" breakpoint
580 thread #1: tid = 0x2c03, stop reason = breakpoint 1.1, queue = com.apple.main-thread