summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPhilip Withnall <pwithnall@endlessos.org>2023-04-28 11:00:33 +0100
committerPhilip Withnall <pwithnall@endlessos.org>2023-04-28 11:00:33 +0100
commit3b9fc716449302c7805b34cae0dde9a88fd99e57 (patch)
tree67999815f240be5581be4a80dcde2655cfb5aaee
parente7398198c5d559c1d88b48b7a02e1320919534a7 (diff)
downloadglib-3b9fc716449302c7805b34cae0dde9a88fd99e57.tar.gz
docs: Mention that calls after fork() must be async-signal-safe
Signed-off-by: Philip Withnall <pwithnall@endlessos.org> Helps: #2958
-rw-r--r--docs/reference/glib/programming.xml9
1 files changed, 8 insertions, 1 deletions
diff --git a/docs/reference/glib/programming.xml b/docs/reference/glib/programming.xml
index 52df907e8..e4cda4cec 100644
--- a/docs/reference/glib/programming.xml
+++ b/docs/reference/glib/programming.xml
@@ -35,8 +35,15 @@ will always have at least 2 threads.
</para>
<para>
+In particular, this means that programs must only use
+<ulink url="man:signal-safety(7)">async-signal-safe functions</ulink> between
+calling <function>fork()</function> and <function>exec()</function>, even if
+they haven’t explicitly spawned another thread yet.
+</para>
+
+<para>
See the sections on <link linkend="glib-Threads">threads</link> and
-<link linkend="glib-Thread-Pools">threadpools</link> for GLib APIs that
+<link linkend="glib-Thread-Pools">thread pools</link> for GLib APIs that
support multithreaded applications.
</para>