diff options
| author | Vedant Kumar <vsk@apple.com> | 2019-10-18 21:05:30 +0000 |
|---|---|---|
| committer | Vedant Kumar <vsk@apple.com> | 2019-10-18 21:05:30 +0000 |
| commit | 32ce14e55e5a99dd99c3b4fd4bd0ccaaf2948c30 (patch) | |
| tree | 96db1514a1898bf521d81c6fe8d0bc591a5d8ee3 /llvm/lib/Support/Windows/Signals.inc | |
| parent | 52d765544b50d2260cf4858ed63c827880b987df (diff) | |
| download | bcm5719-llvm-32ce14e55e5a99dd99c3b4fd4bd0ccaaf2948c30.tar.gz bcm5719-llvm-32ce14e55e5a99dd99c3b4fd4bd0ccaaf2948c30.zip | |
Disable exit-on-SIGPIPE in lldb
Occasionally, during test teardown, LLDB writes to a closed pipe.
Sometimes the communication is inherently unreliable, so LLDB tries to
avoid being killed due to SIGPIPE (it calls `signal(SIGPIPE, SIG_IGN)`).
However, LLVM's default SIGPIPE behavior overrides LLDB's, causing it to
exit with IO_ERR.
Opt LLDB out of the default SIGPIPE behavior. I expect that this will
resolve some LLDB test suite flakiness (tests randomly failing with
IO_ERR) that we've seen since r344372.
rdar://55750240
Differential Revision: https://reviews.llvm.org/D69148
llvm-svn: 375288
Diffstat (limited to 'llvm/lib/Support/Windows/Signals.inc')
| -rw-r--r-- | llvm/lib/Support/Windows/Signals.inc | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/llvm/lib/Support/Windows/Signals.inc b/llvm/lib/Support/Windows/Signals.inc index 6a820ef22b1..d962daf7934 100644 --- a/llvm/lib/Support/Windows/Signals.inc +++ b/llvm/lib/Support/Windows/Signals.inc @@ -560,6 +560,9 @@ void llvm::sys::SetInfoSignalFunction(void (*Handler)()) { // Unimplemented. } +void llvm::sys::SetPipeSignalFunction(void (*Handler)()) { + // Unimplemented. +} /// Add a function to be called when a signal is delivered to the process. The /// handler can have a cookie passed to it to identify what instance of the |
