forked from OSchip/llvm-project
Mention the inline-breakpoint-strategy in the lldb-gdb.html file.
llvm-svn: 175201
This commit is contained in:
parent
7b564da474
commit
719d2c9d36
|
@ -342,6 +342,18 @@
|
|||
</td>
|
||||
</tr>
|
||||
|
||||
<tr><td class="header" colspan="2">Ensure that breakpoints by file and line work for #included .c/.cpp/.m files.</td></tr>
|
||||
|
||||
<tr>
|
||||
<td class="content">
|
||||
<b>(gdb)</b> b foo.c:12<br>
|
||||
</td>
|
||||
<td class="content">
|
||||
<b>(lldb)</b> settings set target.inline-breakpoint-strategy always<br>
|
||||
<b>(lldb)</b> br s -f foo.c -l 12<br>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr><td class="header" colspan="2">Set a breakpoint by regular expression on source file contents.</td></tr>
|
||||
|
||||
<tr>
|
||||
|
|
|
@ -93,6 +93,13 @@
|
|||
<br>(lldb) breakpoint set -n foo
|
||||
</code>
|
||||
|
||||
<p>You can use the --name option multiple times to make a breakpoint on a set of functions as well. This is convenient
|
||||
since it allows you to set commmon conditions or commands without having to specify them multiple times:</p>
|
||||
|
||||
<code>
|
||||
(lldb) breakpoint set --name foo --name bar
|
||||
</code>
|
||||
|
||||
<p>Setting breakpoints by name is even more specialized in LLDB as you can specify
|
||||
that you want to set a breakpoint at a function by method name. To set a breakpoint
|
||||
on all C++ methods named <code>foo</code> you can enter either of:</p>
|
||||
|
@ -117,6 +124,8 @@
|
|||
<br>(lldb) breakpoint set -s foo.dylib -n foo
|
||||
</code>
|
||||
|
||||
<p>The <code>--shlib</code> option can also be repeated to specify several shared libraries.</p>
|
||||
|
||||
<p>Suggestions on more interesting primitives of this sort are also very welcome.</p>
|
||||
|
||||
<p>Just like gdb, the lldb command interpreter does a shortest unique
|
||||
|
|
Loading…
Reference in New Issue