Jason Molenda f17b5ac6e1 <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		2012-12-19 02:54:03 +00:00
..
testsuite	Spelling changes applied from lldb_spelling.diffs from Bruce Mitchener.	2011-01-08 20:28:42 +00:00
building-with-debug-llvm.txt	Instructions for building LLDB with a debug LLVM	2010-11-18 03:56:17 +00:00
code-signing.txt	Avoid potentially disastrous mistakes when removing a file.	2012-11-05 18:41:33 +00:00
lldb-for-gdb-users.txt	Add reference to ToT/examples/customization for more customization examples.	2011-10-12 19:20:04 +00:00
lldb-gdb-remote.txt	<rdar://problem/11961650>	2012-12-19 02:54:03 +00:00
lldb.1	Incorporate suggestions from Jim, add "USING LLDB" and "FILES" sections.	2012-06-08 23:49:32 +00:00
try.me	just a test for commit access - ignore this	2011-06-29 04:18:11 +00:00