luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-02-26 12:12:10 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: Mention that calls after fork() must be async-signal-safe

Browse Source 
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>

Helps: #2958
This commit is contained in:
Philip Withnall 2023-04-28 11:00:33 +01:00
parent e7398198c5
commit 3b9fc71644
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/reference/glib/programming.xml
View File

@ -34,9 +34,16 @@ GLib creates a worker thread for its own purposes so GLib applications
will always have at least 2 threads. will always have at least 2 threads.
</para> </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> <para>
See the sections on <link linkend="glib-Threads">threads</link> and 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. support multithreaded applications.
</para> </para>