Mark the execution of stop-hooks as non-interactive.
authorJim Ingham <jingham@apple.com>
Wed, 28 Oct 2020 18:58:25 +0000 (11:58 -0700)
committerJim Ingham <jingham@apple.com>
Thu, 29 Oct 2020 21:41:53 +0000 (14:41 -0700)
commita37672e2db7377681d996834a0c3073c9838a549
tree450da9a0747a6f2a2589db0e14a92af4056c30c9
parentdb7129a005c105ee17d39a5708d7a5be50df5f47
Mark the execution of stop-hooks as non-interactive.

The intention is not to allow stop-hook commands to query the
user, so this is correct.  It also works around a deadlock in
switching to the Python Session to execute python based commands
in the stop hook when the Debugger stdin is backed by a FILE *.

Differential Revision: https://reviews.llvm.org/D90332
lldb/packages/Python/lldbsuite/test/lldbtest.py
lldb/source/Interpreter/CommandInterpreter.cpp
lldb/source/Target/Target.cpp
lldb/test/API/api/multithreaded/TestMultithreaded.py
lldb/test/API/api/multithreaded/some_cmd.py [new file with mode: 0644]
lldb/test/API/api/multithreaded/test_stop-hook.cpp.template [new file with mode: 0644]