Vedant Kumar 4f6955c715 [Signal] Allow llvm clients to opt into one-shot SIGPIPE handling ... Allow clients of the llvm library to opt-in to one-shot SIGPIPE handling, instead of forcing them to undo llvm's SIGPIPE handler registration (which is brittle). The current behavior is preserved for all llvm-derived tools (except lldb) by means of a default-`true` flag in the InitLLVM constructor. This prevents "IO error" crashes in long-lived processes (lldb is the motivating example) which both a) load llvm as a dynamic library and b) *really* need to ignore SIGPIPE. As llvm signal handlers can be installed when calling into libclang (say, via RemoveFileOnSignal), thereby overriding a previous SIG_IGN for SIGPIPE, there is no clean way to opt-out of "exit-on-SIGPIPE" in the current model. Differential Revision: https://reviews.llvm.org/D70277		2019-11-18 10:27:27 -08:00
..
COM.inc
DynamicLibrary.inc
explicit_symbols.inc
Host.inc
Memory.inc
Path.inc	Win: handle \\?\UNC\ prefix in realPathFromHandle (PR43204)	2019-09-05 09:07:05 +00:00
Process.inc	Reland "[Support] Add a way to run a function on a detached thread""	2019-10-23 15:51:44 +02:00
Program.inc
Signals.inc	[Signal] Allow llvm clients to opt into one-shot SIGPIPE handling	2019-11-18 10:27:27 -08:00
Threading.inc	[Support] fix mingw-w64 build	2019-11-06 15:18:58 +01:00
ThreadLocal.inc
Watchdog.inc
WindowsSupport.h	Reland "[Support] Add a way to run a function on a detached thread""	2019-10-23 15:51:44 +02:00