summaryrefslogtreecommitdiffstats
path: root/llvm/unittests/Support/SignalsTest.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Disable exit-on-SIGPIPE in lldb"Vedant Kumar2019-10-241-54/+0
| | | | | | | This reverts commit 32ce14e55e5a99dd99c3b4fd4bd0ccaaf2948c30. In post-commit review, Pavel pointed out that there's a simpler way to ignore SIGPIPE in lldb that doesn't rely on llvm's handlers.
* Fix llvm signal tests build.David Carlier2019-10-211-0/+1
| | | | llvm-svn: 375406
* Disable exit-on-SIGPIPE in lldbVedant Kumar2019-10-181-0/+53
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
OpenPOWER on IntegriCloud