From 36597e4719e9de6d374f7953aad83234d42ca181 Mon Sep 17 00:00:00 2001 From: Bruce Mitchener Date: Sun, 30 May 2021 21:14:17 +0700 Subject: [PATCH] [lldb] Fix typos. NFC. Differential Revision: https://reviews.llvm.org/D103381 --- lldb/docs/design/overview.rst | 2 +- lldb/docs/resources/test.rst | 2 +- lldb/docs/status/projects.rst | 2 +- lldb/docs/use/python-reference.rst | 4 ++-- lldb/examples/python/process_events.py | 2 +- lldb/include/lldb/Core/Debugger.h | 2 +- lldb/source/API/SBDebugger.cpp | 2 +- lldb/source/Core/ValueObject.cpp | 2 +- .../RenderScript/RenderScriptRuntime/RenderScriptRuntime.cpp | 2 +- lldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp | 2 +- lldb/source/Plugins/Process/Utility/LinuxPTraceDefines_arm64sve.h | 2 +- .../expression/call-function/TestCallUserDefinedFunction.py | 6 +++--- lldb/test/API/lang/c/enum_types/TestEnumTypes.py | 2 +- .../API/lang/cpp/covariant-return-types/TestCovariantReturnTypes.py | 4 ++-- lldb/unittests/Symbol/TestClangASTImporter.cpp | 2 +- 15 files changed, 19 insertions(+), 19 deletions(-) diff --git a/lldb/docs/design/overview.rst b/lldb/docs/design/overview.rst index af98658..06f8370 100644 --- a/lldb/docs/design/overview.rst +++ b/lldb/docs/design/overview.rst @@ -172,7 +172,7 @@ Utility This module contains the lowest layers of LLDB. A lot of these classes don't really have anything to do with debugging -- they are just there because the -higher layers of the debugger use these clasess to implement their +higher layers of the debugger use these classes to implement their functionality. Others are data structures used in many other parts of the debugger (TraceOptions). Most of the functionality in this module could be useful in an application that is not a debugger; however, providing a general diff --git a/lldb/docs/resources/test.rst b/lldb/docs/resources/test.rst index b50b7b2..d2830bc 100644 --- a/lldb/docs/resources/test.rst +++ b/lldb/docs/resources/test.rst @@ -80,7 +80,7 @@ operating systems. Finally, the shell tests always run in batch mode. You start with some input and the test verifies the output. The debugger can be sensitive to its -environment, such as the the platform it runs on. It can be hard to express +environment, such as the platform it runs on. It can be hard to express that the same test might behave slightly differently on macOS and Linux. Additionally, the debugger is an interactive tool, and the shell test provide no good way of testing those interactive aspects, such as tab completion for diff --git a/lldb/docs/status/projects.rst b/lldb/docs/status/projects.rst index 48081da..245654d 100644 --- a/lldb/docs/status/projects.rst +++ b/lldb/docs/status/projects.rst @@ -253,7 +253,7 @@ Use instruction emulation to reduce the overhead for breakpoints At present, breakpoints are implemented by inserting a trap instruction, then when the trap is hit, replace the trap with the actual instruction and single step. Then swap back and continue. This causes problems for read only text, and -also means that no-stop debugging ust either stop all threads briefly to handle +also means that no-stop debugging must either stop all threads briefly to handle this two-step or risk missing some breakpoint hits. If you emulated the instruction and wrote back the results, you wouldn't have these problems, and it would also save a stop per breakpoint hit. Since we use breakpoints to diff --git a/lldb/docs/use/python-reference.rst b/lldb/docs/use/python-reference.rst index 75d9ea1..0c44d5a 100644 --- a/lldb/docs/use/python-reference.rst +++ b/lldb/docs/use/python-reference.rst @@ -315,8 +315,8 @@ a stop for the recursion. For instance, if you request a Module depth search, then the callback will be called for each Module as it gets added to the Target, but the searcher will not recurse into the Compile Units in the module. -One other slight sublety is that the depth at which you get called back is not -necessarily the depth at which the the SearchFilter is specified. For instance, +One other slight subtlety is that the depth at which you get called back is not +necessarily the depth at which the SearchFilter is specified. For instance, if you are doing symbol searches, it is convenient to use the Module depth for the search, since symbols are stored in the module. But the SearchFilter might specify some subset of CompileUnits, so not all the symbols you might find in diff --git a/lldb/examples/python/process_events.py b/lldb/examples/python/process_events.py index 3a1391c..cb4bf78 100755 --- a/lldb/examples/python/process_events.py +++ b/lldb/examples/python/process_events.py @@ -199,7 +199,7 @@ def main(argv): type='string', metavar='DIR', dest='working_dir', - help='The the current working directory when launching a process.', + help='The current working directory when launching a process.', default=None) parser.add_option( '-p', diff --git a/lldb/include/lldb/Core/Debugger.h b/lldb/include/lldb/Core/Debugger.h index 7f25e64..f0849c9 100644 --- a/lldb/include/lldb/Core/Debugger.h +++ b/lldb/include/lldb/Core/Debugger.h @@ -419,7 +419,7 @@ protected: /// \param [in] debugger_id /// If this optional parameter has a value, it indicates the unique /// debugger identifier that this progress should be delivered to. If this - /// optional parameter does not have a value, the the progress will be + /// optional parameter does not have a value, the progress will be /// delivered to all debuggers. static void ReportProgress(uint64_t progress_id, const std::string &message, uint64_t completed, uint64_t total, diff --git a/lldb/source/API/SBDebugger.cpp b/lldb/source/API/SBDebugger.cpp index 8c84c5f..03e6fe5 100644 --- a/lldb/source/API/SBDebugger.cpp +++ b/lldb/source/API/SBDebugger.cpp @@ -170,7 +170,7 @@ const char *SBDebugger::GetProgressFromEvent(const lldb::SBEvent &event, completed = progress_data->GetCompleted(); total = progress_data->GetTotal(); is_debugger_specific = progress_data->IsDebuggerSpecific(); - // We must record the static method _after_ the out paramters have been + // We must record the static method _after_ the out parameters have been // filled in. LLDB_RECORD_STATIC_METHOD( const char *, SBDebugger, GetProgressFromEvent, diff --git a/lldb/source/Core/ValueObject.cpp b/lldb/source/Core/ValueObject.cpp index a6020d2..047fa99 100644 --- a/lldb/source/Core/ValueObject.cpp +++ b/lldb/source/Core/ValueObject.cpp @@ -1577,7 +1577,7 @@ bool ValueObject::IsRuntimeSupportValue() { if (!process) return false; - // We trust the the compiler did the right thing and marked runtime support + // We trust that the compiler did the right thing and marked runtime support // values as artificial. if (!GetVariable() || !GetVariable()->IsArtificial()) return false; diff --git a/lldb/source/Plugins/LanguageRuntime/RenderScript/RenderScriptRuntime/RenderScriptRuntime.cpp b/lldb/source/Plugins/LanguageRuntime/RenderScript/RenderScriptRuntime/RenderScriptRuntime.cpp index dd93122..cd36a83 100644 --- a/lldb/source/Plugins/LanguageRuntime/RenderScript/RenderScriptRuntime/RenderScriptRuntime.cpp +++ b/lldb/source/Plugins/LanguageRuntime/RenderScript/RenderScriptRuntime/RenderScriptRuntime.cpp @@ -2228,7 +2228,7 @@ bool RenderScriptRuntime::RefreshAllocation(AllocationDetails *alloc, return JITAllocationSize(alloc, frame_ptr); } -// Function attempts to set the type_name member of the paramaterised Element +// Function attempts to set the type_name member of the parameterised Element // object. This string should be the name of the struct type the Element // represents. We need this string for pretty printing the Element to users. void RenderScriptRuntime::FindStructTypeName(Element &elem, diff --git a/lldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp b/lldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp index b8f9412..f346f5c 100644 --- a/lldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp +++ b/lldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp @@ -1332,7 +1332,7 @@ void ObjectFileMachO::SanitizeSegmentCommand(segment_command_64 &seg_cmd, if ((m_header.flags & MH_DYLIB_IN_CACHE) && !IsInMemory()) { // In shared cache images, the load commands are relative to the - // shared cache file, and not the the specific image we are + // shared cache file, and not the specific image we are // examining. Let's fix this up so that it looks like a normal // image. if (strncmp(seg_cmd.segname, "__TEXT", sizeof(seg_cmd.segname)) == 0) diff --git a/lldb/source/Plugins/Process/Utility/LinuxPTraceDefines_arm64sve.h b/lldb/source/Plugins/Process/Utility/LinuxPTraceDefines_arm64sve.h index 9e2225f..817dca3 100644 --- a/lldb/source/Plugins/Process/Utility/LinuxPTraceDefines_arm64sve.h +++ b/lldb/source/Plugins/Process/Utility/LinuxPTraceDefines_arm64sve.h @@ -65,7 +65,7 @@ const uint16_t sve_context_size = 16; * The same convention applies when returning from a signal: a caller * will need to remove or resize the sve_context block if it wants to * make the SVE registers live when they were previously non-live or - * vice-versa. This may require the the caller to allocate fresh + * vice-versa. This may require the caller to allocate fresh * memory and/or move other context blocks in the signal frame. * * Changing the vector length during signal return is not permitted: diff --git a/lldb/test/API/commands/expression/call-function/TestCallUserDefinedFunction.py b/lldb/test/API/commands/expression/call-function/TestCallUserDefinedFunction.py index edaa761..8ea7744 100644 --- a/lldb/test/API/commands/expression/call-function/TestCallUserDefinedFunction.py +++ b/lldb/test/API/commands/expression/call-function/TestCallUserDefinedFunction.py @@ -24,13 +24,13 @@ class ExprCommandCallUserDefinedFunction(TestBase): # Test recursive function call. self.expect_expr("fib(5)", result_type="unsigned int", result_value="5") - # Test function with more than one paramter + # Test function with more than one parameter self.expect_expr("add(4, 8)", result_type="int", result_value="12") - # Test nesting function calls in function paramters + # Test nesting function calls in function parameters self.expect_expr("add(add(5,2),add(3,4))", result_type="int", result_value="14") self.expect_expr("add(add(5,2),fib(5))", result_type="int", result_value="12") - # Test function with pointer paramter + # Test function with pointer parameter self.expect_expr('stringCompare((const char*) \"Hello world\")', result_type="bool", result_value="true") self.expect_expr('stringCompare((const char*) \"Hellworld\")', result_type="bool", result_value="false") diff --git a/lldb/test/API/lang/c/enum_types/TestEnumTypes.py b/lldb/test/API/lang/c/enum_types/TestEnumTypes.py index 0442dd3..73d5d5d 100644 --- a/lldb/test/API/lang/c/enum_types/TestEnumTypes.py +++ b/lldb/test/API/lang/c/enum_types/TestEnumTypes.py @@ -137,7 +137,7 @@ class EnumTypesTestCase(TestBase): self.assertEqual(member.signed, value_matches[idx], "Value matches for %d"%(idx)) def test_api(self): - """Test the the SBTypeEnumMember API's work correctly for enum_test_days""" + """Test that the SBTypeEnumMember API's work correctly for enum_test_days""" self.build() target = lldbutil.run_to_breakpoint_make_target(self) diff --git a/lldb/test/API/lang/cpp/covariant-return-types/TestCovariantReturnTypes.py b/lldb/test/API/lang/cpp/covariant-return-types/TestCovariantReturnTypes.py index 6f2b3ea..0e889ea 100644 --- a/lldb/test/API/lang/cpp/covariant-return-types/TestCovariantReturnTypes.py +++ b/lldb/test/API/lang/cpp/covariant-return-types/TestCovariantReturnTypes.py @@ -16,7 +16,7 @@ class TestCase(TestBase): self.expect_expr("base_ptr_to_derived->getPtr()", result_type="Base *") self.expect_expr("base.getPtr()", result_type="Base *") # The same tests with reference types. LLDB drops the reference when it turns the - # result into a SBValue so check for the the underlying type of the result. + # result into a SBValue so check for the underlying type of the result. self.expect_expr("derived.getRef()", result_type="Derived") self.expect_expr("base_ptr_to_derived->getRef()", result_type="Base") self.expect_expr("base.getRef()", result_type="Base") @@ -26,7 +26,7 @@ class TestCase(TestBase): self.expect_expr("base_ptr_to_derived->getOtherPtr()", result_type="OtherBase *") self.expect_expr("base.getOtherPtr()", result_type="OtherBase *") # The same tests with reference types. LLDB drops the reference when it turns the - # result into a SBValue so check for the the underlying type of the result. + # result into a SBValue so check for the underlying type of the result. self.expect_expr("derived.getOtherRef()", result_type="OtherDerived") self.expect_expr("base_ptr_to_derived->getOtherRef()", result_type="OtherBase") self.expect_expr("base.getOtherRef()", result_type="OtherBase") diff --git a/lldb/unittests/Symbol/TestClangASTImporter.cpp b/lldb/unittests/Symbol/TestClangASTImporter.cpp index f1bb451..c8ffd09 100644 --- a/lldb/unittests/Symbol/TestClangASTImporter.cpp +++ b/lldb/unittests/Symbol/TestClangASTImporter.cpp @@ -93,7 +93,7 @@ TEST_F(TestClangASTImporter, CompleteFwdDeclWithOtherOrigin) { clang_utils::SourceASTWithRecord source_with_definition; // Create an AST with a type thst is only a forward declaration with the - // same name as the one in the the other source. + // same name as the one in the other source. std::unique_ptr fwd_decl_source = clang_utils::createAST(); CompilerType fwd_decl_type = clang_utils::createRecord( *fwd_decl_source, source_with_definition.record_decl->getName()); -- 2.7.4