summaryrefslogtreecommitdiffstats
path: root/lldb/docs/use
diff options
context:
space:
mode:
Diffstat (limited to 'lldb/docs/use')
-rw-r--r--lldb/docs/use/map.rst12
-rw-r--r--lldb/docs/use/python-reference.rst2
-rw-r--r--lldb/docs/use/remote.rst4
-rw-r--r--lldb/docs/use/symbolication.rst8
-rw-r--r--lldb/docs/use/troubleshooting.rst2
-rw-r--r--lldb/docs/use/variable.rst4
6 files changed, 16 insertions, 16 deletions
diff --git a/lldb/docs/use/map.rst b/lldb/docs/use/map.rst
index dc8956176df..d878b5633e8 100644
--- a/lldb/docs/use/map.rst
+++ b/lldb/docs/use/map.rst
@@ -110,7 +110,7 @@ Execution Commands
</tr>
<tr>
- <td class="header" colspan="2">Launch a process with arguments in new terminal window (Mac OS X only).</td>
+ <td class="header" colspan="2">Launch a process with arguments in new terminal window (macOS only).</td>
</tr>
<tr>
<td class="content">
@@ -125,7 +125,7 @@ Execution Commands
<tr>
<td class="header" colspan="2">Launch a process with arguments in existing terminal
- <cope>/dev/ttys006 (Mac OS X only).</cope>
+ <cope>/dev/ttys006 (macOS only).</cope>
</td>
</tr>
<tr>
@@ -1385,7 +1385,7 @@ Examining Thread State
</td>
</tr>
<tr>
- <td class="header" colspan="2">Get information about a specific heap allocation (available on Mac OS X only).</td>
+ <td class="header" colspan="2">Get information about a specific heap allocation (available on macOS only).</td>
</tr>
<tr>
<td class="content">
@@ -1401,7 +1401,7 @@ Examining Thread State
</td>
</tr>
<tr>
- <td class="header" colspan="2">Get information about a specific heap allocation and cast the result to any dynamic type that can be deduced (available on Mac OS X only)</td>
+ <td class="header" colspan="2">Get information about a specific heap allocation and cast the result to any dynamic type that can be deduced (available on macOS only)</td>
</tr>
<tr>
<td class="content">
@@ -1414,7 +1414,7 @@ Examining Thread State
</td>
</tr>
<tr>
- <td class="header" colspan="2">Find all heap blocks that contain a pointer specified by an expression EXPR (available on Mac OS X only).</td>
+ <td class="header" colspan="2">Find all heap blocks that contain a pointer specified by an expression EXPR (available on macOS only).</td>
</tr>
<tr>
<td class="content">
@@ -1427,7 +1427,7 @@ Examining Thread State
</td>
</tr>
<tr>
- <td class="header" colspan="2">Find all heap blocks that contain a C string anywhere in the block (available on Mac OS X only).</td>
+ <td class="header" colspan="2">Find all heap blocks that contain a C string anywhere in the block (available on macOS only).</td>
</tr>
<tr>
<td class="content">
diff --git a/lldb/docs/use/python-reference.rst b/lldb/docs/use/python-reference.rst
index 84204f06272..2346947f742 100644
--- a/lldb/docs/use/python-reference.rst
+++ b/lldb/docs/use/python-reference.rst
@@ -672,7 +672,7 @@ Using the lldb.py module in Python
----------------------------------
LLDB has all of its core code build into a shared library which gets used by
-the lldb command line application. On Mac OS X this shared library is a
+the `lldb` command line application. On macOS this shared library is a
framework: LLDB.framework and on other unix variants the program is a shared
library: lldb.so. LLDB also provides an lldb.py module that contains the
bindings from LLDB into Python. To use the LLDB.framework to create your own
diff --git a/lldb/docs/use/remote.rst b/lldb/docs/use/remote.rst
index c0efae08fe0..2ce0639bc10 100644
--- a/lldb/docs/use/remote.rst
+++ b/lldb/docs/use/remote.rst
@@ -76,14 +76,14 @@ system. A list of available plug-ins can be obtained through platform list.
local% lldb
(lldb) platform list
Available platforms:
- host: Local Mac OS X user platform plug-in.
+ host: Local macOS user platform plug-in.
remote-freebsd: Remote FreeBSD user platform plug-in.
remote-linux: Remote Linux user platform plug-in.
remote-netbsd: Remote NetBSD user platform plug-in.
remote-windows: Remote Windows user platform plug-in.
remote-android: Remote Android user platform plug-in.
remote-ios: Remote iOS platform plug-in.
- remote-macosx: Remote Mac OS X user platform plug-in.
+ remote-macosx: Remote macOS user platform plug-in.
ios-simulator: iOS simulator platform plug-in.
darwin-kernel: Darwin Kernel platform plug-in.
tvos-simulator: Apple TV simulator platform plug-in.
diff --git a/lldb/docs/use/symbolication.rst b/lldb/docs/use/symbolication.rst
index 9724628fa1a..9d31b365b98 100644
--- a/lldb/docs/use/symbolication.rst
+++ b/lldb/docs/use/symbolication.rst
@@ -108,7 +108,7 @@ section's file address:
It is often much easier to specify the actual load location of each section by
-name. Crash logs on Mac OS X have a Binary Images section that specifies that
+name. Crash logs on macOS have a Binary Images section that specifies that
address of the __TEXT segment for each binary. Specifying a slide requires
requires that you first find the original (file) address for the __TEXT
segment, and subtract the two values. If you specify the address of the __TEXT
@@ -161,7 +161,7 @@ shared libraries we want:
(lldb) target modules add /usr/lib/system/libsystem_kernel.dylib
-If you have debug symbols in standalone files, such as dSYM files on Mac OS X,
+If you have debug symbols in standalone files, such as dSYM files on macOS,
you can specify their paths using the --symfile option for the ``target create``
(recent LLDB releases only) and ``target modules add`` commands:
@@ -333,14 +333,14 @@ symbolicate an supplied address.
**lldb.macosx.crashlog**
-lldb.macosx.crashlog is a package that is distributed on Mac OS X builds that
+lldb.macosx.crashlog is a package that is distributed on macOS builds that
subclasses the above classes. This module parses the information in the Darwin
crash logs and creates symbolication objects that represent the images, the
sections and the thread frames for the backtraces. It then uses the functions
in the lldb.utils.symbolication to symbolicate the crash logs.
This module installs a new ``crashlog`` command into the lldb command
-interpreter so that you can use it to parse and symbolicate Mac OS X crash
+interpreter so that you can use it to parse and symbolicate macOS crash
logs:
::
diff --git a/lldb/docs/use/troubleshooting.rst b/lldb/docs/use/troubleshooting.rst
index 647b8795c3e..bf858a5870a 100644
--- a/lldb/docs/use/troubleshooting.rst
+++ b/lldb/docs/use/troubleshooting.rst
@@ -42,7 +42,7 @@ breakpoints to have source line information that matches many header file
paths.
If you set a file and line breakpoint using a full path to the source file,
-like Xcode does when setting a breakpoint in its GUI on Mac OS X when you click
+like Xcode does when setting a breakpoint in its GUI on macOS when you click
in the gutter of the source view, this path must match the full paths in the
debug information. If the paths mismatch, possibly due to passing in a resolved
source file path that doesn't match an unresolved path in the debug
diff --git a/lldb/docs/use/variable.rst b/lldb/docs/use/variable.rst
index 01bb9176c04..0e65f42be45 100644
--- a/lldb/docs/use/variable.rst
+++ b/lldb/docs/use/variable.rst
@@ -746,7 +746,7 @@ container classes, regardless of the template arguments provided. The details
for this are found at FormatManager.cpp
The regular expression language used by LLDB is the POSIX extended language, as
-defined by the Single UNIX Specification, of which Mac OS X is a compliant
+defined by the Single UNIX Specification, of which macOS is a compliant
implementation.
Names Summaries
@@ -1032,7 +1032,7 @@ formatters for a same library or OS release.
By default, several categories are created in LLDB:
- default: this is the category where every formatter ends up, unless another category is specified
-- objc: formatters for basic and common Objective-C types that do not specifically depend on Mac OS X
+- objc: formatters for basic and common Objective-C types that do not specifically depend on macOS
- gnu-libstdc++: formatters for std::string, std::vector, std::list and std::map as implemented by libstdcpp
- libcxx: formatters for std::string, std::vector, std::list and std::map as implemented by libcxx
- system: truly basic types for which a formatter is required
OpenPOWER on IntegriCloud