[Lldb-commits] [lldb] [lldb][Mach-O corefiles] Don't init Target arch to corefile (PR #136065)

[via lldb-commits]

github-actions[bot] wrote:

<!--LLVM CODE FORMAT COMMENT: {clang-format}-->


:warning: C/C++ code formatter, clang-format found issues in your code. :warning:

<details>
<summary>
You can test this locally with the following command:
</summary>

``````````bash
git-clang-format --diff HEAD~1 HEAD --extensions cpp -- lldb/source/Plugins/Process/mach-core/ProcessMachCore.cpp
``````````

</details>

<details>
<summary>
View the diff from clang-format here.
</summary>

``````````diff
diff --git a/lldb/source/Plugins/Process/mach-core/ProcessMachCore.cpp b/lldb/source/Plugins/Process/mach-core/ProcessMachCore.cpp
index 4f57c9ade..39584bad2 100644
--- a/lldb/source/Plugins/Process/mach-core/ProcessMachCore.cpp
+++ b/lldb/source/Plugins/Process/mach-core/ProcessMachCore.cpp
@@ -429,7 +429,7 @@ void ProcessMachCore::LoadBinariesViaExhaustiveSearch() {
   // To do an exhaustive search, we'll need to create data extractors
   // to get correctly sized/endianness fields.  If we had a main binary
   // already, we would have set the Target to that - so here we'll use
-  // the corefile's cputype/cpusubtype as the best guess. 
+  // the corefile's cputype/cpusubtype as the best guess.
   if (!GetTarget().GetArchitecture().IsValid()) {
     // The corefile's architecture is our best starting point.
     ArchSpec arch(m_core_module_sp->GetArchitecture());

``````````

</details>


https://github.com/llvm/llvm-project/pull/136065