aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CreateInvocationFromCommandLine.cpp
diff options
context:
space:
mode:
authorMed Ismail Bennani <medismail.bennani@gmail.com>2023-04-14 14:54:01 -0700
committerMed Ismail Bennani <medismail.bennani@gmail.com>2023-04-25 15:02:34 -0700
commit6c961ae1b5073699285fcdec242cdb4e84602c05 (patch)
treed8565a4c9ed6d2a28e81967266000ed6f00aef8a /clang/lib/Frontend/CreateInvocationFromCommandLine.cpp
parent0d77e034749f57676fd79e4a5b560be4d5b52b48 (diff)
downloadllvm-6c961ae1b5073699285fcdec242cdb4e84602c05.zip
llvm-6c961ae1b5073699285fcdec242cdb4e84602c05.tar.gz
llvm-6c961ae1b5073699285fcdec242cdb4e84602c05.tar.bz2
[lldb] Move ScriptedProcess private state update to implementation
While debugging a Scripted Process, in order to update its state and work nicely with lldb's execution model, it needs to toggle its private state from running to stopped, which will result in broadcasting a process state changed event to the debugger listener. Originally, this state update was done systematically in the Scripted Process C++ plugin, however in order to make scripted process interactive, we need to be able to update their state dynamically. This patch makes use of the recent addition of the SBProcess::ForceScriptedState to programatically, and moves the process private state update to the python implementation of the resume method instead of doing it in ScriptedProcess::DoResume. This patch also removes the unused ShouldStop & Stop scripted process APIs, and adds new ScriptedInterface transform methods for boolean arguments. This allow the user to programmatically decide if after running the process, we should stop it (which is the default setting). Differential Revision: https://reviews.llvm.org/D145295 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com>
Diffstat (limited to 'clang/lib/Frontend/CreateInvocationFromCommandLine.cpp')
0 files changed, 0 insertions, 0 deletions