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

Clarify recursion issues with GMutex. (#78171)

Browse Source 
2002-05-01  Sebastian Wilhelmi  <wilhelmi@ira.uka.de>

	* glib/tmpl/threads.sgml: Clarify recursion issues with
	GMutex. (#78171)
This commit is contained in:
Sebastian Wilhelmi 2002-05-01 14:39:48 +00:00 committed by Sebastian Wilhelmi
parent 63ce57cd4d
commit 81d6a7dd7c
2 changed files with 14 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/reference/ChangeLog
View File

@ -1,3 +1,8 @@
2002-05-01 Sebastian Wilhelmi <wilhelmi@ira.uka.de>
* glib/tmpl/threads.sgml: Clarify recursion issues with
GMutex. (#78171)
2002-04-24 Matthias Clasen <maclas@gmx.de>
* gobject/gobject-sections.txt:

16
docs/reference/glib/tmpl/threads.sgml
View File

@ -585,9 +585,10 @@ called and will do nothing then.
<note>
<para>
#GMutex is not recursive, i.e. a thread will deadlock, if it already
has locked @mutex while calling g_mutex_lock(). Use
#GStaticRecMutex instead, if you need recursive mutexes.
#GMutex is neither guaranteed to be recursive nor to be non-recursive,
i.e. a thread could deadlock while calling g_mutex_lock(), if it
already has locked @mutex. Use #GStaticRecMutex, if you need recursive
mutexes.
</para>
</note>
@ -609,9 +610,10 @@ called and will immediately return %TRUE then.
<note>
<para>
#GMutex is not recursive, i.e. g_mutex_trylock() will return %FALSE,
if the current thread already has locked @mutex. Use
#GStaticRecMutex instead, if you need recursive mutexes.
#GMutex is neither guaranteed to be recursive nor to be non-recursive,
i.e. the return value of g_mutex_trylock() could be both %FALSE or
%TRUE, if the current thread already has locked @mutex. Use
#GStaticRecMutex, if you need recursive mutexes.
</para>
</note>
@ -1136,7 +1138,7 @@ g_static_rw_lock_reader_unlock().
<para>
#GStaticRWLock is not recursive. It might seem to be possible to
recursivly lock for reading, but that can result in a deadlock as
recursively lock for reading, but that can result in a deadlock as
well, due to writer preference.
</para>