aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectProcess.cpp
diff options
context:
space:
mode:
authorPavel Labath <pavel@labath.sk>2020-12-17 17:10:17 +0100
committerPavel Labath <pavel@labath.sk>2020-12-17 17:47:53 +0100
commit122a4ebde3f4394a84e9f93b9c7085f088be6dd7 (patch)
tree0cdf9c43e826c3e4d159e06b854520d837efe9ea /lldb/source/Commands/CommandObjectProcess.cpp
parentf50066292477fb26806336e5604615d0eddde399 (diff)
downloadllvm-122a4ebde3f4394a84e9f93b9c7085f088be6dd7.zip
llvm-122a4ebde3f4394a84e9f93b9c7085f088be6dd7.tar.gz
llvm-122a4ebde3f4394a84e9f93b9c7085f088be6dd7.tar.bz2
Revert "[lldb] Make CommandInterpreter's execution context the same as debugger's one."
This reverts commit a01b26fb51c710a3a8ef88cc83b0701461f5b9ab, because it breaks the "finish" command in some way -- the command does not terminate after it steps out, but continues running the target. The exact blast radius is not clear, but it at least affects the usage of the "finish" command in TestGuiBasicDebug.py. The error is *not* gui-related, as the same issue can be reproduced by running the same steps outside of the gui. There is some kind of a race going on, as the test fails only 20% of the time on the buildbot.
Diffstat (limited to 'lldb/source/Commands/CommandObjectProcess.cpp')
-rw-r--r--lldb/source/Commands/CommandObjectProcess.cpp1
1 files changed, 1 insertions, 0 deletions
diff --git a/lldb/source/Commands/CommandObjectProcess.cpp b/lldb/source/Commands/CommandObjectProcess.cpp
index 8beabed..1eef280 100644
--- a/lldb/source/Commands/CommandObjectProcess.cpp
+++ b/lldb/source/Commands/CommandObjectProcess.cpp
@@ -380,6 +380,7 @@ protected:
return false;
}
+ m_interpreter.UpdateExecutionContext(nullptr);
StreamString stream;
const auto error = target->Attach(m_options.attach_info, &stream);
if (error.Success()) {