summaryrefslogtreecommitdiff
path: root/deps/uv/docs/src/signal.rst
diff options
context:
space:
mode:
Diffstat (limited to 'deps/uv/docs/src/signal.rst')
-rw-r--r--deps/uv/docs/src/signal.rst24
1 files changed, 18 insertions, 6 deletions
diff --git a/deps/uv/docs/src/signal.rst b/deps/uv/docs/src/signal.rst
index f52b64706a..f5a809ab0b 100644
--- a/deps/uv/docs/src/signal.rst
+++ b/deps/uv/docs/src/signal.rst
@@ -6,7 +6,10 @@
Signal handles implement Unix style signal handling on a per-event loop bases.
-Reception of some signals is emulated on Windows:
+Windows notes
+-------------
+
+Reception of some signals is emulated:
* SIGINT is normally delivered when the user presses CTRL+C. However, like
on Unix, it is not generated when terminal raw mode is enabled.
@@ -24,13 +27,22 @@ Reception of some signals is emulated on Windows:
* Calls to raise() or abort() to programmatically raise a signal are
not detected by libuv; these will not trigger a signal watcher.
-.. note::
- On Linux SIGRT0 and SIGRT1 (signals 32 and 33) are used by the NPTL pthreads library to
- manage threads. Installing watchers for those signals will lead to unpredictable behavior
- and is strongly discouraged. Future versions of libuv may simply reject them.
-
.. versionchanged:: 1.15.0 SIGWINCH support on Windows was improved.
+Unix notes
+----------
+
+* SIGKILL and SIGSTOP are impossible to catch.
+
+* Handling SIGBUS, SIGFPE, SIGILL or SIGSEGV via libuv results into undefined behavior.
+
+* SIGABRT will not be caught by libuv if generated by `abort()`, e.g. through `assert()`.
+
+* On Linux SIGRT0 and SIGRT1 (signals 32 and 33) are used by the NPTL pthreads library to
+ manage threads. Installing watchers for those signals will lead to unpredictable behavior
+ and is strongly discouraged. Future versions of libuv may simply reject them.
+
+
Data types
----------