Before this patch if you used SBThread.StepUsingScriptedThreadPlan but mistyped the Python ThreadPlan class name, you wouldn't get any error, and a bogus ThreadPlan would get executed. This patch adds an error string and plumbs it through to where we look up the Python class, so now you get a decent error string. We also tell ourselves the plan has failed (by returning an empty StructuredObject) so that the plan will fail the IsValid check and so not get pushed.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM