[lldb] Fix platform selection on Apple Silicon (again)

[JDevlieghere]

Summary

This patch is another attempt to fix platform selection on Apple Silicon. It partially undoes D117340 which tried to fix the issue by always instantiating a remote-ios platform for "iPhone and iPad Apps on Apple Silicon Macs". While the previous patch worked for attaching, it broke launching and everything else that expects the remote platform to be connected. I made an attempt to work around that, but quickly found out that there were just too may places that had this assumption baked in.

This patch takes a different approach and reverts back to marking the host platform compatible with iOS triples. This brings us back to the original situation where platform selection was broken for remote iOS debugging on Apple Silicon. To fix that, I now look at the process' system architecture to differentiate between iOS binaries running remotely and iOS binaries running locally. I wish I could make this distinction in the platform, but you need a connected process to do this.

I tested the following scenarios, which now all uses the desired platform:

• Launching an iOS binary on macOS: uses the host platform
• Attaching to an iOS binary on macOS: uses the host platform
• Attaching to a remote iOS binary: uses the remote-ios platform

rdar://89840215

[JDevlieghere]

Include TargetConditionals.h

[labath]

I wish I could make this distinction in the platform, but you need a connected process to do this.

Basically, what you're saying is that the ArchSpec alone is not sufficient to select the right platform. Instead of punching right through the layers, could we just give more information (which I guess would be the system architecture) to the functions responsible for selecting the right plugin? Then they could do the regular ask-each-plugin-if-it-wants-to-handle-it dance. The host plugin would say "I don't handle processes with system-arch=*-ios" and then we would go around until we find the remote-ios plugin saying "I live for debugging ios systems"?

[I must admit that I have a bit of an ulterior motive for suggesting this -- I also have a use case where the ArchSpec is not sufficient to select the best platform, but I've struggled to formulate it in a way that makes sense upstream. The system architecture is not relevant for my case (what I'd really need is to inspect the details of the executable being debugged -- mainly its path, but possibly also some other bits), but if we open the door to more elaborate platform selection, then I might be able to squeeze this in as well.

[JDevlieghere]

In D121444#3374854, @labath wrote:

I wish I could make this distinction in the platform, but you need a connected process to do this.

Basically, what you're saying is that the ArchSpec alone is not sufficient to select the right platform. Instead of punching right through the layers, could we just give more information (which I guess would be the system architecture) to the functions responsible for selecting the right plugin? Then they could do the regular ask-each-plugin-if-it-wants-to-handle-it dance. The host plugin would say "I don't handle processes with system-arch=*-ios" and then we would go around until we find the remote-ios plugin saying "I live for debugging ios systems"?

[I must admit that I have a bit of an ulterior motive for suggesting this -- I also have a use case where the ArchSpec is not sufficient to select the best platform, but I've struggled to formulate it in a way that makes sense upstream. The system architecture is not relevant for my case (what I'd really need is to inspect the details of the executable being debugged -- mainly its path, but possibly also some other bits), but if we open the door to more elaborate platform selection, then I might be able to squeeze this in as well.

Yup, that could totally work, it didn't seem worth like changing all that for just the one use case, but happy to do it if you can benefit from that as well. Did you have any particular design in mind? For me, passing an extra ArchSpec for the host arch would do the trick, but that doesn't get you much further. I could pass in a little context object which would hold an ArchSpec for the host arch and a FileSpec for your use case. Or maybe we should just pass in the process if we have one and get all the information from that.

[labath]

In D121444#3375445, @JDevlieghere wrote:

In D121444#3374854, @labath wrote:

I wish I could make this distinction in the platform, but you need a connected process to do this.

Basically, what you're saying is that the ArchSpec alone is not sufficient to select the right platform. Instead of punching right through the layers, could we just give more information (which I guess would be the system architecture) to the functions responsible for selecting the right plugin? Then they could do the regular ask-each-plugin-if-it-wants-to-handle-it dance. The host plugin would say "I don't handle processes with system-arch=*-ios" and then we would go around until we find the remote-ios plugin saying "I live for debugging ios systems"?

[I must admit that I have a bit of an ulterior motive for suggesting this -- I also have a use case where the ArchSpec is not sufficient to select the best platform, but I've struggled to formulate it in a way that makes sense upstream. The system architecture is not relevant for my case (what I'd really need is to inspect the details of the executable being debugged -- mainly its path, but possibly also some other bits), but if we open the door to more elaborate platform selection, then I might be able to squeeze this in as well.

Yup, that could totally work, it didn't seem worth like changing all that for just the one use case, but happy to do it if you can benefit from that as well. Did you have any particular design in mind? For me, passing an extra ArchSpec for the host arch would do the trick, but that doesn't get you much further. I could pass in a little context object which would hold an ArchSpec for the host arch and a FileSpec for your use case. Or maybe we should just pass in the process if we have one and get all the information from that.

A process wouldn't help me, since I am primarily interested in the launch scenario, where the platform is selected long before the process is launched. I am contemplating passing in a ModuleSpec instead of a plain ArchSpec. That would be sufficient for my use case, but I don't know if I really like it (it seems somewhat strange because the we would really like to pass in the process architecture, but a ModuleSpec would normally describe the module architecture (which may be less precise)). So, it may be best to have a specialized context object, but at the end of the day, I don't think that's something that you need to solve. I think it would be sufficient to just add an additional ArchSpec argument for now. If that idea proves itself (and I decide to go ahead with this), I can upgrade that to a context object.

[JDevlieghere]

In D121444#3375701, @labath wrote:

In D121444#3375445, @JDevlieghere wrote:

In D121444#3374854, @labath wrote:

I wish I could make this distinction in the platform, but you need a connected process to do this.

Basically, what you're saying is that the ArchSpec alone is not sufficient to select the right platform. Instead of punching right through the layers, could we just give more information (which I guess would be the system architecture) to the functions responsible for selecting the right plugin? Then they could do the regular ask-each-plugin-if-it-wants-to-handle-it dance. The host plugin would say "I don't handle processes with system-arch=*-ios" and then we would go around until we find the remote-ios plugin saying "I live for debugging ios systems"?

[I must admit that I have a bit of an ulterior motive for suggesting this -- I also have a use case where the ArchSpec is not sufficient to select the best platform, but I've struggled to formulate it in a way that makes sense upstream. The system architecture is not relevant for my case (what I'd really need is to inspect the details of the executable being debugged -- mainly its path, but possibly also some other bits), but if we open the door to more elaborate platform selection, then I might be able to squeeze this in as well.

Yup, that could totally work, it didn't seem worth like changing all that for just the one use case, but happy to do it if you can benefit from that as well. Did you have any particular design in mind? For me, passing an extra ArchSpec for the host arch would do the trick, but that doesn't get you much further. I could pass in a little context object which would hold an ArchSpec for the host arch and a FileSpec for your use case. Or maybe we should just pass in the process if we have one and get all the information from that.

A process wouldn't help me, since I am primarily interested in the launch scenario, where the platform is selected long before the process is launched. I am contemplating passing in a ModuleSpec instead of a plain ArchSpec. That would be sufficient for my use case, but I don't know if I really like it (it seems somewhat strange because the we would really like to pass in the process architecture, but a ModuleSpec would normally describe the module architecture (which may be less precise)). So, it may be best to have a specialized context object, but at the end of the day, I don't think that's something that you need to solve. I think it would be sufficient to just add an additional ArchSpec argument for now. If that idea proves itself (and I decide to go ahead with this), I can upgrade that to a context object.

Cool, that works for me

[JDevlieghere]

Check the host architecture in PlatformMacOSX

[labath]

I don't suppose we could have a (gdb-client?) test for some of this stuff?

lldb/source/Plugins/Platform/MacOSX/PlatformMacOSX.cpp

159

if (!host_arch || host_arch.GetTriple().getOS() == llvm::Triple::MacOSX)

...

[JDevlieghere]

Add tests

[JDevlieghere]

Fix typo(s)

[labath]

Cool.

lldb/source/Plugins/Platform/MacOSX/PlatformDarwin.h

protected:
 
   void ReadLibdispatchOffsets(lldb_private::Process *process);
 
   virtual lldb_private::Status GetSharedModuleWithLocalCache(
       const lldb_private::ModuleSpec &module_spec, lldb::ModuleSP &module_sp,
       const lldb_private::FileSpecList *module_search_paths_ptr,
       llvm::SmallVectorImpl<lldb::ModuleSP> *old_modules, bool *did_create_ptr);
 
-  virtual bool CheckLocalSharedCache() const { return IsHost(); }
+  bool CheckLocalSharedCache() const { return IsHost(); }
 
   struct SDKEnumeratorInfo {
     lldb_private::FileSpec found_path;
     lldb_private::XcodeSDK::Type sdk_type;
   };
 
   static lldb_private::FileSystem::EnumerateDirectoryResult
   DirectoryEnumerator(void *baton, llvm::sys::fs::file_type file_type,

lldb/source/Plugins/Platform/MacOSX/PlatformMacOSX.cpp

#if defined(__arm__) || defined(__arm64__) || defined(__aarch64__)
   if (host_os == llvm::Triple::MacOSX) {
     // We can't use x86GetSupportedArchitectures() because it uses
     // the system architecture for some of its return values and also
     // has a 32bits variant.
     result.push_back(ArchSpec("x86_64-apple-macosx"));
     result.push_back(ArchSpec("x86_64-apple-ios-macabi"));
     result.push_back(ArchSpec("arm64-apple-ios-macabi"));
     result.push_back(ArchSpec("arm64e-apple-ios-macabi"));
+    result.push_back(ArchSpec("arm64-apple-ios"));
+    result.push_back(ArchSpec("arm64e-apple-ios"));
   }
 #else
   x86GetSupportedArchitectures(result);
   result.push_back(ArchSpec("x86_64-apple-ios-macabi"));
 #endif
   return result;
 }
 
 lldb_private::Status PlatformMacOSX::GetSharedModule(
     const lldb_private::ModuleSpec &module_spec, Process *process,
     lldb::ModuleSP &module_sp,
     const lldb_private::FileSpecList *module_search_paths_ptr,

lldb/source/Plugins/Platform/MacOSX/PlatformRemoteiOS.h

public:
   llvm::StringRef GetDescription() override { return GetDescriptionStatic(); }
 
   // lldb_private::PluginInterface functions
   llvm::StringRef GetPluginName() override { return GetPluginNameStatic(); }
 
   std::vector<lldb_private::ArchSpec> GetSupportedArchitectures() override;
 
 protected:
-  bool CheckLocalSharedCache() const override;
-
   llvm::StringRef GetDeviceSupportDirectoryName() override;
   llvm::StringRef GetPlatformName() override;
 };
 
 #endif // LLDB_SOURCE_PLUGINS_PLATFORM_MACOSX_PLATFORMREMOTEIOS_H

lldb/source/Plugins/Platform/MacOSX/PlatformRemoteiOS.cpp

PlatformRemoteiOS::PlatformRemoteiOS()
     : PlatformRemoteDarwinDevice() {}
 
 std::vector<ArchSpec> PlatformRemoteiOS::GetSupportedArchitectures() {
   std::vector<ArchSpec> result;
   ARMGetSupportedArchitectures(result, llvm::Triple::IOS);
   return result;
 }
 
-bool PlatformRemoteiOS::CheckLocalSharedCache() const {
-  // You can run iPhone and iPad apps on Mac with Apple Silicon. At the
-  // platform level there's no way to distinguish them from remote iOS
-  // applications. Make sure we still read from our own shared cache.
-  return true;
-}
-
 llvm::StringRef PlatformRemoteiOS::GetDeviceSupportDirectoryName() {
   return "iOS DeviceSupport";
 }
 
 llvm::StringRef PlatformRemoteiOS::GetPlatformName() {
   return "iPhoneOS.platform";
 }

lldb/source/Target/Process.cpp

 #include "lldb/Utility/LLDBLog.h"
 #include "lldb/Utility/Log.h"
 #include "lldb/Utility/NameMatches.h"
 #include "lldb/Utility/ProcessInfo.h"
 #include "lldb/Utility/SelectHelper.h"
 #include "lldb/Utility/State.h"
 #include "lldb/Utility/Timer.h"
 
+#if defined(__APPLE__)
+#include <TargetConditionals.h>
+#endif
+
 using namespace lldb;
 using namespace lldb_private;
 using namespace std::chrono;
 
 // Comment out line below to disable memory caching, overriding the process
 // setting target.process.disable-memory-cache
 #define ENABLE_MEMORY_CACHING
 

                   "Process::%s switching architecture to %s based on info "
                   "the platform retrieved for pid %" PRIu64,
                   __FUNCTION__, process_arch.GetTriple().getTriple().c_str(),
                   GetID());
       }
     }
   }
 
+#if TARGET_OS_OSX
+#if defined(__arm__) || defined(__arm64__) || defined(__aarch64__)
+  // On Apple Silicon the host platform is compatible with arm64(e)-apple-ios
+  // to support unmodified "iPhone and iPad Apps on Apple Silicon Macs".
+  //
+  // Because the binaries are identical and platform selection relies on the
+  // triple, there's no way to differentiate the two statically. Once we have a
+  // process, we can use its system architecture to tell the two apart and
+  // change the platform if necessary.
+  if (platform_sp->GetPluginName() == "host") {
+    llvm::Triple target_triple = GetTarget().GetArchitecture().GetTriple();
+    if (target_triple.getOS() == llvm::Triple::IOS &&
+        target_triple.getVendor() == llvm::Triple::Apple) {
+      llvm::Triple system_triple = GetSystemArchitecture().GetTriple();
+      if (system_triple.getOS() == llvm::Triple::IOS) {
+        Status error;
+        GetTarget().SetPlatform(
+            Platform::Create(ConstString("remote-ios"), error));
+      }
+    }
+  }
+#endif
+#endif
+
   // We have completed the attach, now it is time to find the dynamic loader
   // plug-in
   DynamicLoader *dyld = GetDynamicLoader();
   if (dyld) {
     dyld->DidAttach();
     if (log) {
       ModuleSP exe_module_sp = GetTarget().GetExecutableModule();
       LLDB_LOG(log,