Any commands that are executed through the public interface using SBCommandInterprete...
authorGreg Clayton <gclayton@apple.com>
Tue, 15 Jul 2014 00:25:59 +0000 (00:25 +0000)
committerGreg Clayton <gclayton@apple.com>
Tue, 15 Jul 2014 00:25:59 +0000 (00:25 +0000)
commit45a44f3c4da7969ee8534ad16ea841ff301f6b1c
tree62e6fb51666e5c7e45aa89d2c48294474e661e55
parent5a477c5e372bde1f96c1146b5a68f02c7e93f40b
Any commands that are executed through the public interface using SBCommandInterpreter::HandleCommand() are assumed to be in non-interactive mode.

Any commands that want interactivity (stdin) will need to be executed through the normal command interpreter using the debugger's in/out/err file handles, or by using "command source".

Individual commands through the API will have their STDIN disabled. The STDOUT and STDERR will be redirected into the SBCommandReturnObject argument to SBCommandInterpreter::HandleCommand() as usual.

This helps with a deadlock situation in an IDE (Xcode) where the IDE was managing the breakpoint actions by setting a breakpoint callback and doing things manually.

<rdar://problem/17386271>

llvm-svn: 213023
lldb/include/lldb/Interpreter/CommandReturnObject.h
lldb/source/API/SBCommandInterpreter.cpp
lldb/source/Interpreter/CommandReturnObject.cpp
lldb/source/Interpreter/ScriptInterpreterPython.cpp