aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptedProcessPythonInterface.h
diff options
context:
space:
mode:
authorRaphael Isemann <teemperor@gmail.com>2021-07-22 15:31:12 +0200
committerRaphael Isemann <teemperor@gmail.com>2021-07-22 15:35:28 +0200
commiteb61ffbcb277cfaeb459d6d38b34ba908d247f96 (patch)
tree51e348af2208fbc5bba33f81ad4c3ca87cc2b83b /lldb/source/Plugins/ScriptInterpreter/Python/ScriptedProcessPythonInterface.h
parentf6413d8aaa0205b58345bdd985d2c5c4544bd260 (diff)
downloadllvm-eb61ffbcb277cfaeb459d6d38b34ba908d247f96.zip
llvm-eb61ffbcb277cfaeb459d6d38b34ba908d247f96.tar.gz
llvm-eb61ffbcb277cfaeb459d6d38b34ba908d247f96.tar.bz2
[lldb] Fix TestCompletion by using SIGPIPE instead of SIGINT as test signal
The test I added in commit 078003482e90ff5c7ba047a3d3152f0b0c392b31 was using SIGINT for testing the tab completion. The idea is to have a signal that only has one possible completion and I ended up picking SIGIN -> SIGINT for the test. However on non-Linux systems there is SIGINFO which is a valid completion for `SIGIN' and so the test fails there. This replaces SIGIN -> SIGINT with SIGPIP -> SIGPIPE completion which according to LLDB's signal list in Host.cpp is the only valid completion.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptedProcessPythonInterface.h')
0 files changed, 0 insertions, 0 deletions