summaryrefslogtreecommitdiffstats
path: root/lldb/source/Target/ThreadPlanStepOverRange.cpp
diff options
context:
space:
mode:
authorJim Ingham <jingham@apple.com>2013-02-09 01:29:05 +0000
committerJim Ingham <jingham@apple.com>2013-02-09 01:29:05 +0000
commit0161b49cbadd54431b4acefa8dae954ebef12ec8 (patch)
tree2f6c58512e07b7d65af0a6de0a0fd9df6e1d6013 /lldb/source/Target/ThreadPlanStepOverRange.cpp
parent1aa79e9f637d9f5fb514095e8b29108bd15c261f (diff)
downloadbcm5719-llvm-0161b49cbadd54431b4acefa8dae954ebef12ec8.tar.gz
bcm5719-llvm-0161b49cbadd54431b4acefa8dae954ebef12ec8.zip
Reworked the way Process::RunThreadPlan and the ThreadPlanCallFunction interoperate to fix problems where
hitting auto-continue signals while running a thread plan would cause us to lose control of the debug session. <rdar://problem/12993641> llvm-svn: 174793
Diffstat (limited to 'lldb/source/Target/ThreadPlanStepOverRange.cpp')
-rw-r--r--lldb/source/Target/ThreadPlanStepOverRange.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/lldb/source/Target/ThreadPlanStepOverRange.cpp b/lldb/source/Target/ThreadPlanStepOverRange.cpp
index 7851f7081d7..a00d5cc84ef 100644
--- a/lldb/source/Target/ThreadPlanStepOverRange.cpp
+++ b/lldb/source/Target/ThreadPlanStepOverRange.cpp
@@ -290,7 +290,7 @@ ThreadPlanStepOverRange::ShouldStop (Event *event_ptr)
}
bool
-ThreadPlanStepOverRange::PlanExplainsStop ()
+ThreadPlanStepOverRange::PlanExplainsStop (Event *event_ptr)
{
// For crashes, breakpoint hits, signals, etc, let the base plan (or some plan above us)
// handle the stop. That way the user can see the stop, step around, and then when they
OpenPOWER on IntegriCloud