Searched refs:SetPlanComplete (Results 1 - 9 of 9) sorted by relevance

/freebsd-10.3-release/contrib/llvm/tools/lldb/source/Target/
H A DThreadPlanStepInstruction.cpp121 SetPlanComplete();
166 SetPlanComplete();
174 SetPlanComplete();
185 SetPlanComplete();
H A DThreadPlanStepThrough.cpp164 SetPlanComplete(true);
173 SetPlanComplete();
193 SetPlanComplete(false);
208 SetPlanComplete();
H A DThreadPlanStepOut.cpp186 SetPlanComplete();
238 SetPlanComplete();
283 SetPlanComplete();
300 SetPlanComplete ();
315 SetPlanComplete();
H A DThreadPlanCallFunction.cpp232 SetPlanComplete(success);
303 SetPlanComplete();
388 SetPlanComplete(false);
538 SetPlanComplete(false);
H A DThreadPlanStepInRange.cpp115 SetPlanComplete();
175 SetPlanComplete();
244 SetPlanComplete();
H A DThreadPlanStepUntil.cpp220 SetPlanComplete();
270 SetPlanComplete();
H A DThreadPlan.cpp79 ThreadPlan::SetPlanComplete (bool success) function in class:ThreadPlan
H A DThreadPlanStepOverRange.cpp289 SetPlanComplete();
/freebsd-10.3-release/contrib/llvm/tools/lldb/include/lldb/Target/
H A DThreadPlan.h156 // SetPlanComplete and the ThreadPlan implementation of MischiefManaged will return "true", without your having
157 // to redo the calculation when your sub-classes MischiefManaged is called. If you call SetPlanComplete, you can
161 // One slightly tricky point is you have to be careful using SetPlanComplete in PlanExplainsStop because you
174 // the stop reason, then it can call SetPlanComplete and pass in "false" for the "success" parameter. In that case,
455 SetPlanComplete (bool success = true);

Completed in 109 milliseconds