<rdar://problem/11961650>
authorJason Molenda <jmolenda@apple.com>
Wed, 19 Dec 2012 02:54:03 +0000 (02:54 +0000)
committerJason Molenda <jmolenda@apple.com>
Wed, 19 Dec 2012 02:54:03 +0000 (02:54 +0000)
commitf17b5ac6e1239a5ff8c46c0351ba140b35f7a6ab
treeb88ee14026d17dae8cc22635ac01bb24e808eede
parent503053a737bf1c54899bcc2d1b4c514485e30054
<rdar://problem/11961650>

Update the debugserver "qProcessInfo" implementation to return the
cpu type, cpu subtype, OS and vendor information just like qHostInfo
does so lldb can create an ArchSpec based on the returned values.

Add a new GetProcessArchitecture to GDBRemoteCommunicationClient akin
to GetHostArchitecture.  If the qProcessInfo packet is supported,
GetProcessArchitecture will return the cpu type / subtype of the
process -- e.g. a 32-bit user process running on a 64-bit x86_64 Mac
system.

Have ProcessGDBRemote set the Target's architecture based on the
GetProcessArchitecture when we've completed an attach/launch/connect.

llvm-svn: 170491
lldb/docs/lldb-gdb-remote.txt
lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp
lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.h
lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
lldb/tools/debugserver/source/RNBRemote.cpp