The DynamicLoader plug-in instance now lives up in lldb_private::Process where

it should live and the lldb_private::Process takes care of managing the 
auto pointer to the dynamic loader instance.

Also, now that the ArchSpec contains the target triple, we are able to 
correctly set the Target architecture in DidLaunch/DidAttach in the subclasses,
and then the lldb_private::Process will find the dynamic loader plug-in 
by letting the dynamic loader plug-ins inspect the arch/triple in the target.

So now the ProcessGDBRemote plug-in is another step closer to be purely 
process/platform agnostic.

I updated the ProcessMacOSX and the ProcessLinux plug-ins accordingly.

llvm-svn: 125650

1 files changed, 4 insertions, 0 deletions

diff --git a/lldb/tools/debugserver/source/RNBRemote.cpp b/lldb/tools/debugserver/source/RNBRemote.cpp
index e1b8fc4103c..1d6d0883c23 100644
--- a/lldb/tools/debugserver/source/RNBRemote.cpp
+++ b/lldb/tools/debugserver/source/RNBRemote.cpp
@@ -3258,7 +3258,11 @@ RNBRemote::HandlePacket_qHostInfo (const char *p)
     char ostype[64];
     len = sizeof(ostype);
     if (::sysctlbyname("kern.ostype", &ostype, &len, NULL, 0) == 0)
+    {
+        len = strlen(ostype);
+        std::transform (ostype, ostype + len, ostype, tolower);
         strm << "ostype:" << std::dec << ostype << ';';
+    }
 
     strm << "vendor:apple;";