llvm-project/lldb
Jim Ingham 2656af95eb Don't use !eStateRunning when you mean eStateStopped in DestroyImpl.
When we go to destroy the process, we first try to halt it, if
we succeeded and the target stopped, we want to clear out the
thread plans and breakpoints in case we still need to resume to complete
killing the process.  If the target was exited or detached, it's
pointless but harmless to do this.  But if the state is eStateInvalid -
for instance if we tried to interrupt the target to Halt it and that
fails - we don't want to keep trying to interact with the inferior,
so we shouldn't do this work.

This change explicitly checks eStateStopped, and only does the pre-resume
cleanup if we did manage to stop the process.
2021-07-19 14:30:04 -07:00
..
bindings [lldb] Add AllocateMemory/DeallocateMemory to the SBProcess API 2021-07-16 00:45:22 +02:00
cmake
docs [lldb][docs] Remove mention of subversion. NFC. 2021-07-14 11:04:07 +00:00
examples
include/lldb [trace][intel pt] Implement the Intel PT cursor 2021-07-16 16:47:43 -07:00
packages/Python [LLDB] Testsuite: Add helper to check for AArch64 target 2021-07-12 14:21:45 +05:00
resources
scripts
source Don't use !eStateRunning when you mean eStateStopped in DestroyImpl. 2021-07-19 14:30:04 -07:00
test [trace][intel pt] Implement the Intel PT cursor 2021-07-16 16:47:43 -07:00
third_party/Python/module
tools [debugserver] Un-conditionalize code guarded by macOS 10.10 checks 2021-07-15 23:18:05 -07:00
unittests [lldb][AArch64] Add tag packing and repetition memory tag manager 2021-07-16 14:21:38 +01:00
utils
.clang-format
.clang-tidy
.gitignore
CMakeLists.txt
CODE_OWNERS.txt
LICENSE.TXT
use_lldb_suite_root.py