================ @@ -0,0 +1,41 @@ +""" +Test that `target frame-provider register` succeeds without asserting. + +CommandObjectTargetFrameProviderRegister::DoExecute never called +CommandReturnObject::SetStatus() on its success path. CommandObject.cpp +has a DoExecuteStatusCheck RAII guard that asserts DoExecute always sets a +status; since AppendMessage()/AppendMessageWithFormatv() don't touch +status (unlike AppendError()/SetError(), which do), the status stayed +eReturnStatusInvalid on success, tripping the assert. + +This regression went unnoticed because every other scripted_frame_provider +test calls SBTarget::RegisterScriptedFrameProvider directly, bypassing +this command entirely. +""" + +import os +import lldb +import lldbsuite.test.lldbutil as lldbutil +from lldbsuite.test.decorators import * +from lldbsuite.test.lldbtest import * + + +class TestFrameProviderRegisterCommandStatus(TestBase): ---------------- medismailben wrote:
I've been matching the filename for the test class name for too long, so calling this TestCase feels weird to me. I'll stick with this. https://github.com/llvm/llvm-project/pull/208232 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
