Add two additional DNBLog's in places where we're about to kill
off the inferior process so we stand a better chance of understanding
what caused us to send a PT_KILL.
<rdar://problem/12720340>
llvm-svn: 177817
diff --git a/lldb/tools/debugserver/source/RNBRemote.cpp b/lldb/tools/debugserver/source/RNBRemote.cpp
index 2670051..4c515f4 100644
--- a/lldb/tools/debugserver/source/RNBRemote.cpp
+++ b/lldb/tools/debugserver/source/RNBRemote.cpp
@@ -3836,6 +3836,7 @@
rnb_err_t
RNBRemote::HandlePacket_k (const char *p)
{
+ DNBLog ("Got a 'k' packet, killing the inferior process.");
// No response to should be sent to the kill packet
if (m_ctx.HasValidProcessID())
DNBProcessKill (m_ctx.ProcessID());
diff --git a/lldb/tools/debugserver/source/debugserver.cpp b/lldb/tools/debugserver/source/debugserver.cpp
index ecafaaf..4fcc0a1 100644
--- a/lldb/tools/debugserver/source/debugserver.cpp
+++ b/lldb/tools/debugserver/source/debugserver.cpp
@@ -571,6 +571,7 @@
// in its current state and listen for another connection...
if (ctx.ProcessStateRunning())
{
+ DNBLog ("debugserver's event read thread is exiting, killing the inferior process.");
DNBProcessKill (ctx.ProcessID());
}
}