Don't need to figure out the frame's module if we don't have any libraries
in the step-avoid-libraries list.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@199944 91177308-0d34-0410-b5e6-96231b3b80d8
Move process launching into GDBRemoteCommunicationServer.

lldb-gdbserver was launching the commandline-specified launch process
directly, without GDBRemoteCommunicationServer knowing anything about
it.  As GDBRemoteCommunicationServer is the piece that manages and
knows about processes that the gdb remote protocol discusses with
the client end, it is important that it know about launched processes.

This change also implements the k gdb remote protocol message, having it
kill all known spawned processes when it is received.

(Note: in lldb-gdbserver, the spawned processes are not properly
monitored yet. The response to the k packet will complain that
spawned processes do not really appear to be getting killed even if
they are. This will get addressed soon.)



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@199945 91177308-0d34-0410-b5e6-96231b3b80d8
Updated to latest and greatest demangler sources.

<rdar://problem/15736085>



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@199946 91177308-0d34-0410-b5e6-96231b3b80d8
Fixed a test suite exception that was cause by bad python (sys.unlink instead of os.unlink).



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