[Lldb-commits] [lldb] [lldb] Make use of Scripted{Python, }Interface for ScriptedThreadPlan (PR #70392)

[David Spickett via lldb-commits]

DavidSpickett wrote:

So in case it was confusing, the revert did fix Arm 32 bit linux as well, but it stayed red for other reasons.

Also I looked into it on the same machine and got:
```
********************
Unresolved Tests (1):
  lldb-api :: functionalities/thread_plan/TestThreadPlanCommands.py

********************
Failed Tests (3):
  lldb-api :: functionalities/completion/TestCompletion.py
  lldb-api :: functionalities/step_scripted/TestStepScripted.py
  lldb-shell :: Commands/command-stop-hook-output.test
```
Same tests as on x86. One failed with:
```
FAIL: LLDB (/home/david.spickett/build-arm/bin/clang-arm) :: test_thread_plan_actions (TestThreadPlanCommands.TestThreadPlanCommands)
======================================================================
ERROR: test_thread_plan_actions (TestThreadPlanCommands.TestThreadPlanCommands)
----------------------------------------------------------------------
TypeError: WrapStepOver.__init__() missing 1 required positional argument: 'dict'
```
And I see that the previous special case Python object maker thingy (can you tell I know nothing about this :) ) did pass on, or make a dict of some sort.

The others seemed to be trying to create a plan, which failed (same reason I expect), then tried to use it which of course failed.

https://github.com/llvm/llvm-project/pull/70392