summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndrew Kaylor <andrew.kaylor@intel.com>2012-12-07 17:56:31 +0000
committerAndrew Kaylor <andrew.kaylor@intel.com>2012-12-07 17:56:31 +0000
commit327c267a9561d52e691b732c0f0dcfea4ddebeae (patch)
tree6f221cf570f187f0ea82daa74ec6f68a09b720e3
parent131186c11a297eb67a46e5f0b6dff4a69eeaf394 (diff)
downloadbcm5719-llvm-327c267a9561d52e691b732c0f0dcfea4ddebeae.tar.gz
bcm5719-llvm-327c267a9561d52e691b732c0f0dcfea4ddebeae.zip
Set ThreadPlanCallFunction to private in ConstructorSetup. This fixes a problem on Linux where 'continue' was misfiring after an expression evaluation when stopped at a breakpoint. The problem was that InferiorCallMmap was not setting its ThreadPlanCallFunction to private and so the completion of that thread plan appeared to be the stop reason and therefore the 'continue' operation failed to step over the breakpoint. The SetPrivate call is being put in ThreadPlanCallFunction rather than InferiorCallMmap to make the solution more general.
llvm-svn: 169618
-rw-r--r--lldb/source/Target/ThreadPlanCallFunction.cpp1
1 files changed, 1 insertions, 0 deletions
diff --git a/lldb/source/Target/ThreadPlanCallFunction.cpp b/lldb/source/Target/ThreadPlanCallFunction.cpp
index a17b3b6ce72..9e768641f05 100644
--- a/lldb/source/Target/ThreadPlanCallFunction.cpp
+++ b/lldb/source/Target/ThreadPlanCallFunction.cpp
@@ -44,6 +44,7 @@ ThreadPlanCallFunction::ConstructorSetup (Thread &thread,
{
SetIsMasterPlan (true);
SetOkayToDiscard (false);
+ SetPrivate (true);
ProcessSP process_sp (thread.GetProcess());
if (!process_sp)
OpenPOWER on IntegriCloud