diff --git a/lldb/docs/lldb-gdb-remote.txt b/lldb/docs/lldb-gdb-remote.txt index 3b808642eb7c..6a70dc02c64b 100644 --- a/lldb/docs/lldb-gdb-remote.txt +++ b/lldb/docs/lldb-gdb-remote.txt @@ -1086,7 +1086,7 @@ tuples to return are: If the address requested is not in a mapped region (e.g. we've jumped through a NULL pointer and are at 0x0) currently lldb expects to get back the size of the unmapped region -- that is, the distance to the next valid region. -For instance, with a Mac OS X process which has nothing mapped in the first +For instance, with a macOS process which has nothing mapped in the first 4GB of its address space, if we're asking about address 0x2, qMemoryRegionInfo:2 @@ -1611,7 +1611,7 @@ for this region. // // Because this is a JSON string, the thread number is provided in base10. // Additional key-value pairs may be provided by lldb to the gdb remote -// stub. For instance, on some versions of Mac OS X, lldb can read offset +// stub. For instance, on some versions of macOS, lldb can read offset // information out of the system libraries. Using those offsets, debugserver // is able to find the Thread Specific Address (TSD) for a thread and include // that in the return information. So lldb will send these additional fields @@ -1620,7 +1620,7 @@ for this region. // jThreadExtendedInfo:{"plo_pthread_tsd_base_address_offset":0,"plo_pthread_tsd_base_offset":224,"plo_pthread_tsd_entry_size":8,"thread":612910} // // There are no requirements for what is included in the response. A simple -// reply on a Mac OS X Yosemite / iOS 8 may include the pthread_t value, the +// reply on a OS X Yosemite / iOS 8 may include the pthread_t value, the // Thread Specific Data (TSD) address, the dispatch_queue_t value if the thread // is associated with a GCD queue, and the requested Quality of Service (QoS) // information about that thread. For instance, a reply may look like: @@ -1740,7 +1740,7 @@ for this region. // out of memory with generic read packets) but also adds additional information in the form of the // filename of the shared libraries (which is not available in the mach-o header/load commands.) // -// An example using the Mac OS X 10.11 style call: +// An example using the OS X 10.11 style call: // // LLDB SENDS: jGetLoadedDynamicLibrariesInfos:{"image_count":1,"image_list_address":140734800075128} // STUB REPLIES: ${"images":[{"load_address":4294967296,"mod_date":0,"pathname":"/tmp/a.out","uuid":"02CF262C-ED6F-3965-9E14-63538B465CFF","mach_header":{"magic":4277009103,"cputype":16777223,"cpusubtype":18446744071562067971,"filetype":2},"segments":{"name":"__PAGEZERO","vmaddr":0,"vmsize":4294967296,"fileoff":0,"filesize":0,"maxprot":0},{"name":"__TEXT","vmaddr":4294967296,"vmsize":4096,"fileoff":0,"filesize":4096,"maxprot":7},{"name":"__LINKEDIT","vmaddr":4294971392,"vmsize":4096,"fileoff":4096,"filesize":152,"maxprot":7}}]}#00 @@ -1797,7 +1797,7 @@ for this region. // would need to work correctly on this platform. // // PRIORITY TO IMPLEMENT -// On Mac OS X 10.11, iOS 9, tvOS 9, watchOS 2 and older: Low. If this packet is absent, +// On OS X 10.11, iOS 9, tvOS 9, watchOS 2 and older: Low. If this packet is absent, // lldb will read the Mach-O headers/load commands out of memory. // On macOS 10.12, iOS 10, tvOS 10, watchOS 3 and newer: High. If this packet is absent, // lldb will not know anything about shared libraries in the inferior, or where the main diff --git a/lldb/docs/resources/build.rst b/lldb/docs/resources/build.rst index 23f5f4e5bb6f..e8d99f7a2219 100644 --- a/lldb/docs/resources/build.rst +++ b/lldb/docs/resources/build.rst @@ -113,7 +113,7 @@ and the working directory to point to binaries inside of the ninja tree. Building LLDB on macOS ---------------------- -There are two ways to build LLDB on Mac OS X: Using Xcode and using CMake +There are two ways to build LLDB on macOS: Using Xcode and using CMake **Preliminaries** @@ -122,13 +122,12 @@ There are two ways to build LLDB on Mac OS X: Using Xcode and using CMake **Building LLDB with Xcode** -Building on Mac OS X with Xcode is as easy as downloading the code and building +Building on macOS with Xcode is as easy as downloading the code and building the Xcode project or workspace: * Download the lldb sources. * Follow the code signing instructions in ``lldb/docs/code-signing.txt``. -* In Xcode 3.x: ``lldb/lldb.xcodeproj``, select the lldb-tool target, and build. -* In Xcode 4.x: ``lldb/lldb.xcworkspace``, select the lldb-tool scheme, and build. +* In Xcode, open ``lldb/lldb.xcworkspace``, select the lldb-tool scheme, and build. **Building LLDB with CMake** diff --git a/lldb/docs/status/about.rst b/lldb/docs/status/about.rst index 0a7ea230d2da..c0f38afa013b 100644 --- a/lldb/docs/status/about.rst +++ b/lldb/docs/status/about.rst @@ -37,7 +37,7 @@ Reusability The LLDB debugger APIs are exposed as a C++ object oriented interface in a shared library. The lldb command line tool links to, and uses this public API. -On Mac OS X the shared library is exposed as a framework named LLDB.framework, +On macOS the shared library is exposed as a framework named LLDB.framework, and unix systems expose it as lldb.so. The entire API is also then exposed through Python script bindings which allow the API to be used within the LLDB embedded script interpreter, and also in any python script that loads the @@ -54,7 +54,7 @@ Platform Support LLDB is known to work on the following platforms, but ports to new platforms are welcome: -* Mac OS X desktop user space debugging for i386 and x86-64 +* macOS desktop user space debugging for i386 and x86-64 * iOS simulator debugging on i386 * iOS device debugging on ARM * Linux local user-space debugging for i386, x86-64 and PPC64le diff --git a/lldb/docs/status/features.rst b/lldb/docs/status/features.rst index 43eb7408b01c..2ce581f3f282 100644 --- a/lldb/docs/status/features.rst +++ b/lldb/docs/status/features.rst @@ -13,6 +13,6 @@ LLDB supports a broad variety of basic debugging features such as reading DWARF, * Debugger plug-ins implement the host and target specific functions required to debug. * SWIG-generated script bridging allows Python to access and control the public API of the debugger library. -* A remote protocol server, debugserver, implements Mac OS X debugging on i386 and x86-64. +* A remote protocol server, debugserver, implements macOS debugging on i386 and x86-64. * A command line debugger - the lldb executable itself. * A framework API to the library. diff --git a/lldb/docs/status/status.rst b/lldb/docs/status/status.rst index b114bdd9743f..21db2ac8c1c3 100644 --- a/lldb/docs/status/status.rst +++ b/lldb/docs/status/status.rst @@ -6,7 +6,7 @@ macOS LLDB has matured a lot in the last year and can be used for C, C++ and Objective-C development for x86_64, i386 and ARM debugging. The entire public -API is exposed though a framework on Mac OS X which is used by Xcode, the lldb +API is exposed though a framework on macOS which is used by Xcode, the lldb command line tool, and can also be used by Python. The entire public API is exposed through script bridging which allows LLDB to use an embedded Python script interpreter, as well as having a Python module named "lldb" which can be @@ -40,7 +40,7 @@ section below. Features Matrix --------------- +--------------------------------+------------+-------------------------+--------------------------------------+----------------------+ -| Feature | FreeBSD | Linux | Mac OS X (i386/x86_64 and ARM/Thumb) | Windows (i386) | +| Feature | FreeBSD | Linux | macOS (i386/x86_64 and ARM/Thumb) | Windows (i386) | | | (x86_64) | (x86_64 and PPC64le) | | | +================================+============+=========================+======================================+======================+ | Backtracing | OK | OK | OK | OK | diff --git a/lldb/docs/testsuite/a-detailed-walkthrough.txt b/lldb/docs/testsuite/a-detailed-walkthrough.txt index be679ef353de..fff5a40d1da7 100644 --- a/lldb/docs/testsuite/a-detailed-walkthrough.txt +++ b/lldb/docs/testsuite/a-detailed-walkthrough.txt @@ -123,7 +123,7 @@ And the test/plugins/darwin.py provides the implementation for all three build methods using the makefile mechanism. We envision that linux plugin can use a similar approach to accomplish the task of building the binaries. -Mac OS X provides an additional way to manipulate archived DWARF debug symbol +macOS provides an additional way to manipulate archived DWARF debug symbol files and produces dSYM files. The buildDsym() instance method is used by the test method to build the binary with dsym info. For an example of this, see test/array_types/TestArrayTypes.py: diff --git a/lldb/docs/use/map.rst b/lldb/docs/use/map.rst index dc8956176df5..d878b5633e83 100644 --- a/lldb/docs/use/map.rst +++ b/lldb/docs/use/map.rst @@ -110,7 +110,7 @@ Execution Commands