diff options
Diffstat (limited to 'lldb/www')
| -rwxr-xr-x | lldb/www/formats.html | 2 | ||||
| -rwxr-xr-x | lldb/www/index.html | 2 | ||||
| -rwxr-xr-x | lldb/www/lldb-gdb.html | 6 | ||||
| -rwxr-xr-x | lldb/www/python-reference.html | 4 | ||||
| -rwxr-xr-x | lldb/www/scripting.html | 2 | ||||
| -rwxr-xr-x | lldb/www/tutorial.html | 2 |
6 files changed, 9 insertions, 9 deletions
diff --git a/lldb/www/formats.html b/lldb/www/formats.html index 9e994cb5cdb..b40dd9740aa 100755 --- a/lldb/www/formats.html +++ b/lldb/www/formats.html @@ -91,7 +91,7 @@ <tr valign=top><td><b>module.file.fullpath</b></td><td>The basename of the current module (shared library or executable)</td></tr> <tr valign=top><td><b>process.file.basename</b></td><td>The basename of the file for the process</td></tr> <tr valign=top><td><b>process.file.fullpath</b></td><td>The fullname of the file for the process</td></tr> - <tr valign=top><td><b>process.id</b></td><td>The process ID native the the system on which the inferior runs.</td></tr> + <tr valign=top><td><b>process.id</b></td><td>The process ID native to the system on which the inferior runs.</td></tr> <tr valign=top><td><b>process.name</b></td><td>The name of the process at runtime</td></tr> <tr valign=top><td><b>thread.id</b></td><td>The thread identifier for the current thread</td></tr> <tr valign=top><td><b>thread.index</b></td><td>The unique one based thread index ID which is guaranteed to be unique as threads come and go.</td></tr> diff --git a/lldb/www/index.html b/lldb/www/index.html index 3b77b95ece5..d0003e0384a 100755 --- a/lldb/www/index.html +++ b/lldb/www/index.html @@ -56,7 +56,7 @@ language features and runtimes in expressions without having to reimplement <b>any</b> of this functionality. It also leverages the compiler to take care of all ABI details when making functions calls for expressions, when disassembling - instructions and extracting instruciton details, and much more. + instructions and extracting instruction details, and much more. <p>The major benefits include:</p> <ul> <li>Up to date language support for C, C++, Objective C</li> diff --git a/lldb/www/lldb-gdb.html b/lldb/www/lldb-gdb.html index 1a9299accdc..803c87080c6 100755 --- a/lldb/www/lldb-gdb.html +++ b/lldb/www/lldb-gdb.html @@ -616,7 +616,7 @@ </td> </tr> - <tr><td class="header" colspan="2">Display a the variable "argc" and "argv" every time you stop.</td></tr> + <tr><td class="header" colspan="2">Display the variables "argc" and "argv" every time you stop.</td></tr> <tr> <td class="content"> <b>(gdb)</b> display argc<br> @@ -630,7 +630,7 @@ </td> </tr> - <tr><td class="header" colspan="2">Display a the variable "argc" and "argv" only when you stop in the function named <b>main</b>.</td></tr> + <tr><td class="header" colspan="2">Display the variables "argc" and "argv" only when you stop in the function named <b>main</b>.</td></tr> <tr> <td class="content"> </td> @@ -1157,7 +1157,7 @@ </td> </tr> - <tr><td class="header" colspan="2">Find full souce line information.</td></tr> + <tr><td class="header" colspan="2">Find full source line information.</td></tr> <tr> <td class="content"> <b>(gdb)</b> info line 0x1ec4<br> diff --git a/lldb/www/python-reference.html b/lldb/www/python-reference.html index dfc2165ee5c..f70f538b527 100755 --- a/lldb/www/python-reference.html +++ b/lldb/www/python-reference.html @@ -322,7 +322,7 @@ Enter your Python command(s). Type 'DONE' to end. <p>Python functions can be used to create new LLDB command interpreter commands, which will work like all the natively defined lldb commands. This provides a very flexible and easy way to extend LLDB to meet your debugging requirements. </p> - <p>To write a python function that implements a new LDB command define the function to take four arguments as follows:</p> + <p>To write a python function that implements a new LLDB command define the function to take four arguments as follows:</p> <code><pre><tt>def command_function(<b>debugger</b>, <b>command</b>, <b>result</b>, <b>internal_dict</b>): <font color=green># Your code goes here</font> @@ -414,7 +414,7 @@ Enter your Python command(s). Type 'DONE' to end. <lldb> module at the top of the python <b>ls.py</b> module. This test must be in code that isn't contained inside of any function or class, just like the standard test for <b>__main__</b> like all python modules - usally do. Sample code would look like: + usually do. Sample code would look like: <code><pre><tt>if __name__ == '__main__': <font color=green># Create a new debugger instance in your module if your module diff --git a/lldb/www/scripting.html b/lldb/www/scripting.html index 7e86acfaa8e..10ba05b6a10 100755 --- a/lldb/www/scripting.html +++ b/lldb/www/scripting.html @@ -520,7 +520,7 @@ Process 696 stopped <p>After setting our breakpoints, adding our breakpoint commands and continuing, we run for a little bit and then hit one of our breakpoints, printing out the - error message from the breakpoint command. Apparently at this point the the + error message from the breakpoint command. Apparently at this point in the tree, our search algorithm decided to go right, but our path says the node we want is to the left. Examining the word at the node where we stopped, and our search word, we see:</p> diff --git a/lldb/www/tutorial.html b/lldb/www/tutorial.html index bbab90de2c4..d144b71ef85 100755 --- a/lldb/www/tutorial.html +++ b/lldb/www/tutorial.html @@ -77,7 +77,7 @@ foo.c) got more and more complex and bizarre, and especially in C++ there are times where there's really no way to specify the function you want to break on. The lldb commands are more verbose but also more precise - and allow for intellegent auto completion. + and allow for intelligent auto completion. <p>To set the same file and line breakpoint in LLDB you can enter either of:</p> |
