In CommandObjectRegisterRead.DoExecute(), set the status to "success" when appropriate.
Diff Detail
Event Timeline
Thanks for the patch. Could you please also add an appropriate test for it? Doing something similar to what packages/Python/lldbsuite/test/functionalities/frame_var/TestFrameVar.py does should be the easiest way to test this.
It can make sense to add
assert(eReturnStatusStarted != result);
after cmd_obj->Execute() invocation at CommandInterpreter::HandleCommand, do you think?
that sounds like an excellent idea, as it will check all executed commands, and not the ones we've remembered checking. It should probably be an lldbassert though. (And we'd need to check that the existing tests still pass after that.)
Yes: lldbassert would be fine for that since those get compiled out during release. Patch looks fine. If we already have a test that would trigger the new "lldbassert" you will add, then no need for a special test for this, else we need a test that triggers this.
I will try to ensure that the lldbassert gets tested, but right now, none of the tests work on my machine. I emailed lldb-dev for help.
This is sure to trigger things in the test suite. We will need to ensure a few things:
- test suite runs cleanly in debug mode after the lldbassert is added
- without changes to CommandObjectRegister.cpp that the lldbassert is triggered, and if not, add a test