summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Support
diff options
context:
space:
mode:
authorTodd Fiala <tfiala@google.com>2014-01-23 22:05:44 +0000
committerTodd Fiala <tfiala@google.com>2014-01-23 22:05:44 +0000
commit403edc5c57b608585b94c93a648333231a9c68c7 (patch)
treea3e7f3f652ab7e5822046300a579766f6e3f1602 /llvm/lib/Support
parenta786e53903c08e0d0f04c92b0f32e83005e252ce (diff)
downloadbcm5719-llvm-403edc5c57b608585b94c93a648333231a9c68c7.tar.gz
bcm5719-llvm-403edc5c57b608585b94c93a648333231a9c68c7.zip
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.) llvm-svn: 199945
Diffstat (limited to 'llvm/lib/Support')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud