jingham added a comment. Each new command invocation is expected to prime the ExecutionContext before invoking the command. I don't think there's any situation where one command should use a previous command's execution context on purpose. So if we're getting to Execute without the CommandInterpreter having proactively set the ExecutionContext for that invocation, that is a bug that should be fixed. This change will make sure that the incorrectly inherited ExecutionContext is empty, but that still means the command is somehow getting invoked with the wrong execution context.
Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D132397/new/ https://reviews.llvm.org/D132397 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
