summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/Process
diff options
context:
space:
mode:
authorJason Molenda <jmolenda@apple.com>2015-04-17 05:01:58 +0000
committerJason Molenda <jmolenda@apple.com>2015-04-17 05:01:58 +0000
commitede3193bbd336bd817b918b348243fc3bfc3ab6b (patch)
tree895b41ba17b787373ca6c6ac5b10ebeb2d040bb8 /lldb/source/Plugins/Process
parent66eda7323c8e627d8e796c6fac012d99d6fa3341 (diff)
downloadbcm5719-llvm-ede3193bbd336bd817b918b348243fc3bfc3ab6b.tar.gz
bcm5719-llvm-ede3193bbd336bd817b918b348243fc3bfc3ab6b.zip
Add a "force_kill" arg to Process::Destroy(). This is needed after
the changes in r233255/r233258. Normally if lldb attaches to a running process, when we call Process::Destroy, we want to detach from the process. If lldb launched the process itself, ::Destroy should kill it. However, if we attach to a process and the driver calls SBProcess::Kill() (which calls Destroy), we need to kill it even if we didn't launch it originally. The force_kill param allows for the SBProcess::Kill method to force the behavior of Destroy. <rdar://problem/20424439> llvm-svn: 235158
Diffstat (limited to 'lldb/source/Plugins/Process')
-rw-r--r--lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp b/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
index dc61ec839da..da3a650e789 100644
--- a/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
+++ b/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
@@ -2166,7 +2166,7 @@ ProcessGDBRemote::DoDestroy ()
}
}
Resume ();
- return Destroy();
+ return Destroy(false);
}
}
}
OpenPOWER on IntegriCloud