Now that setting an architecture from a mach-o CPU type and subtype doesn't set the OS type, make sure to set it.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@214600 91177308-0d34-0410-b5e6-96231b3b80d8
After you attach, give the process plugin a chance to report back (through
DidAttach) the architecture of the binary you attached to.

<rdar://problem/17891396>


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@214603 91177308-0d34-0410-b5e6-96231b3b80d8
Make the swig generation script use the correct python executable.

It was hardcoding the value "python", which will end up at best
getting a different python executable (if the user has overridden
the value of PYTHON_EXECUTABLE), and at worst encountering an
error (if there is no copy of python on the system path).

This patch changes the script to use sys.executable so that it
runs the sub-script with the same executable that it was run with.

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@214618 91177308-0d34-0410-b5e6-96231b3b80d8
Change ProcessGDBRemote::DidLaunchOrAttach to 
call Target::SetArchitecture instead of modifying a
reference to the target's architecture so that the
target logging can show that the arch has been changed.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@214667 91177308-0d34-0410-b5e6-96231b3b80d8