en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/python_api/debugger/Makefile#36de94cf Reland "[lldb] Make CommandInterpreter's execution context the same as debugger's one" List of files: /llvm-project-15.0.7/lldb/test/API/python_api/debugger/Makefile Fri, 18 Dec 2020 13:36:15 +0000 Tatyana Krasnukha <tatyana@synopsys.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/python_api/debugger/Makefile#a01b26fb [lldb] Make CommandInterpreter's execution context the same as debugger's one.Currently, the interpreter's context is not updated until a command is executed.This has resulted in the behavior of SB-interface functions and some commandsdepends on previous user actions. The interpreter's context can stay uninitialized,point to a currently selected target, or point to one of previously selected targets.This patch removes any usages of CommandInterpreter::UpdateExecutionContext.CommandInterpreter::HandleCommand* functions still may override context temporarily,but now they always restore it before exiting. CommandInterpreter saves overridencontexts to the stack, that makes nesting commands possible.Added test reproduces one of the issues. Without this fix, the last assertion failsbecause interpreter's execution context is empty until running "target list", so,the value of the global property was updated instead of process's local instance.Differential Revision: https://reviews.llvm.org/D92164 List of files: /llvm-project-15.0.7/lldb/test/API/python_api/debugger/Makefile Thu, 10 Dec 2020 16:30:04 +0000 Tatyana Krasnukha <21970096+tkrasnukha@users.noreply.github.com>